Mobile device cover for use with a host mobile device

ABSTRACT

A mobile device cover for use with a host mobile device includes a front frame, a middle frame, and a back frame. The back frame includes a plate or portion that can be removed and interchanged with a second plate or portion. The second plate or portion can be designed to look different and to provide different functionality. For example, the plate or portion of the back frame can be replaced with the second interchangeable plate or portion to provide a screen that can be used by one or both of the mobile device cover and the host mobile device.

FIELD OF THE DISCLOSURE

Certain embodiments of the disclosure relate to systems and methods forcontrolling a mobile device cover for use with a mobile device.

BACKGROUND OF THE DISCLOSURE

Conventional mobile phone covers are passive accessories to mobilephones. They can have static designs and can offer some measure ofprotection for the mobile phone.

Further limitations and disadvantages of conventional and traditionalapproaches will become apparent to one of skill in the art, throughcomparison of such systems with the present disclosure as set forth inthe remainder of the present application with reference to the drawings.

BRIEF SUMMARY OF THE DISCLOSURE

Some embodiments according to the present disclosure relate to, forexample, an active cover for an electronic device or equipment asillustrated by and/or described in connection with at least one of thefigures, as set forth more completely in the claims.

Various advantages, aspects and novel features of the presentdisclosure, as well as details of an illustrated embodiment thereof,will be more fully understood from the following description anddrawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIG. 1A shows an exemplary mobile device cover according to anembodiment of the present disclosure.

FIG. 1B shows a top view of an exemplary mobile device cover accordingto an embodiment of the present disclosure.

FIG. 1C shows a partially exploded side perspective view of an exemplarymobile device cover according to an embodiment of the presentdisclosure.

FIG. 1D shows an exploded side perspective view of an exemplary mobiledevice cover according to an embodiment of the present disclosure.

FIG. 1E shows an exemplary mobile device cover according to anembodiment of the present disclosure.

FIG. 1F shows a front side of a front portion of an exemplary mobiledevice cover according to an embodiment of the present disclosure.

FIG. 1G shows a front side of a middle portion of an exemplary mobiledevice cover according to an embodiment of the present disclosure.

FIG. 2 shows an exemplary circuit arrangement according to an embodimentof the present disclosure.

FIG. 3 shows an exemplary launch screen page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 4 shows an exemplary front page of a mobile application accordingto an embodiment of the present disclosure.

FIG. 5 shows an exemplary connection page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 6 shows an exemplary instructions page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 7 shows an exemplary home page of a mobile application according toan embodiment of the present disclosure.

FIG. 8 shows an exemplary lightshows page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 9 shows an exemplary assigned contacts page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 10 shows an exemplary icons page of a mobile application accordingto an embodiment of the present disclosure.

FIG. 11A shows an exemplary scrolling text page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 11B shows another exemplary scrolling text page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 12 shows an exemplary add item page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 13 shows an exemplary notifications-for-applications page of amobile application according to an embodiment of the present disclosure.

FIG. 14 shows an exemplary lighting-for-contacts page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 15 shows an exemplary lightshows-for-contacts page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 16 shows an exemplary icons-for-contacts page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 17 shows an exemplary battery page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 18 shows an exemplary lighting page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 19 shows an exemplary clock page of a mobile application accordingto an embodiment of the present disclosure.

FIG. 20 shows an exemplary back design page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 21 shows an exemplary settings page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 22 shows an exemplary notifications-for-applications settings pageof a mobile application according to an embodiment of the presentdisclosure.

FIG. 23 shows an exemplary lightshows-for-contacts settings page of amobile application according to an embodiment of the present disclosure.

FIG. 24 shows an exemplary synchronization/reset page of a mobileapplication according to an embodiment of the present disclosure.

FIG. 25A shows an exemplary preview as a portion of an exemplary page ofa mobile application according to an embodiment of the presentdisclosure.

FIG. 25B shows an exemplary preview page of a mobile applicationaccording to an embodiment of the present disclosure.

FIG. 25C shows an exemplary preview on a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 25D shows an exemplary preview on a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 25E shows an exemplary preview on a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 26 shows a front view of an exemplary middle frame of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 27 shows a back view of an exemplary middle frame of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 28 shows a side view of an exemplary middle frame of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 29 shows a perspective view of an exemplary middle frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 30 shows a front view of an exemplary front frame of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 31 shows a back view of an exemplary front frame of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 32 shows a side view of an exemplary front frame of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 33 shows a perspective view of an exemplary front frame of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 34 shows a front view of an exemplary back frame of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 35 shows a back view of an exemplary back frame of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 36 shows a side view of an exemplary back frame of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 37 shows a perspective view of an exemplary back frame of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 38 shows a front view of an exemplary button structure of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 39 shows a back view of an exemplary button structure of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 40 shows a side view of an exemplary button structure of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 41 shows a perspective view of an exemplary button structure of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 42 shows a perspective view of an exemplary middle frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 43 shows an exemplary cushion disposed in an exemplary middle frameof a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 44 shows an exemplary host mobile device disposed in an exemplarymiddle frame of a mobile device cover according to an embodiment of thepresent disclosure.

FIG. 45 shows an exemplary front frame mounted on an exemplary middleframe of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 46 shows an exemplary port connector disposed in an exemplarymiddle frame of a mobile device cover according to an embodiment of thepresent disclosure.

FIG. 47 shows an exemplary first screw screwed in an exemplary middleframe of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 48 shows an exemplary second screw screwed in an exemplary middleframe of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 49 shows an exemplary battery disposed in an exemplary middle frameof a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 50 shows exemplary wires of an exemplary battery disposed in anexemplary middle frame of a mobile device cover according to anembodiment of the present disclosure.

FIG. 51 shows exemplary wires of an exemplary port connector disposed inan exemplary middle frame of a mobile device cover according to anembodiment of the present disclosure.

FIG. 52 shows an exemplary printed circuit board mounted over theexemplary battery in an exemplary middle frame of a mobile device coveraccording to an embodiment of the present disclosure.

FIG. 53 shows an exemplary printed circuit board mounted over theexemplary battery by an exemplary first screw in an exemplary middleframe of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 54 shows an exemplary printed circuit board mounted over theexemplary battery by an exemplary second screw in an exemplary middleframe of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 55 shows an exemplary button structure disposed in an exemplarymiddle frame of a mobile device cover according to an embodiment of thepresent disclosure.

FIG. 56 shows an exemplary back frame mounted on an exemplary middleframe of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 57 shows an exploded view of an exemplary mobile device coveraccording to an embodiment of the present disclosure.

FIG. 58 shows an exploded view of an exemplary mobile device coveraccording to an embodiment of the present disclosure.

FIG. 59 shows an exemplary USB-to-connector circuit of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 60 shows an exemplary push button circuit of a mobile device coveraccording to an embodiment of the present disclosure.

FIG. 61 shows an exemplary battery charge indicator circuit of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 62 shows an exemplary memory circuit of a mobile device coveraccording to an embodiment of the present disclosure.

FIG. 63 shows an exemplary processor circuit of a mobile device coveraccording to an embodiment of the present disclosure.

FIG. 64 shows an exemplary battery management circuit of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 65 shows an exemplary power management circuit of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 66 shows an exemplary off/on and/or reset circuit of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 67 shows an exemplary clock circuit of a mobile device coveraccording to an embodiment of the present disclosure.

FIG. 68 shows an exemplary Bluetooth circuit of a mobile device coveraccording to an embodiment of the present disclosure.

FIG. 69 shows an exemplary LED driver circuit of a mobile device coveraccording to an embodiment of the present disclosure.

FIG. 70A shows an exemplary LED array of a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 70B shows an exemplary LED array of a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 70C shows an exemplary LED array of a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 70D shows an exemplary LED array of a mobile device cover accordingto an embodiment of the present disclosure.

FIG. 71 shows an exemplary multi-layer printed circuit board of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 72 shows an exemplary top layer of a multi-layer printed circuitboard of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 73 shows an exemplary second layer of a multi-layer printed circuitboard of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 74 shows an exemplary third layer of a multi-layer printed circuitboard of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 75 shows an exemplary bottom layer of a multi-layer printed circuitboard of a mobile device cover according to an embodiment of the presentdisclosure.

FIG. 76 shows an exemplary removable portion of a back frame of a mobiledevice cover according to an embodiment of the present disclosure.

FIG. 77A shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 77B shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 78A shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 78B shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 79A shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 79B shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 79C shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 79D shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 79E shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 79F shows an exemplary removable portion of a back frame of amobile device cover according to an embodiment of the presentdisclosure.

FIG. 80A shows an exemplary removable back frame of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 80B shows an exemplary removable back frame of a mobile devicecover according to an embodiment of the present disclosure.

FIG. 81 shows an exemplary removable back cover of a host mobile deviceaccording to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

As utilized herein the terms “circuit” and “circuitry” refer to physicalelectronic components (i.e., hardware) and any software and/or firmware(“code”) which may configure the hardware, be executed by the hardware,and/or otherwise be associated with the hardware. As utilized herein,“and/or” means any one or more of the items in the list joined by“and/or”. As an example, “x and/or y” means any element of thethree-element set {(x), (y), (x, y)}. As another example, “x, y, and/orz” means any element of the seven-element set {(x), (y), (z), (x, y),(x, z), (y, z), (x, y, z)}. As utilized herein, the term “exemplary”means serving as a non-limiting example, instance, or illustration. Asutilized herein, the terms “e.g.,” and “for example” set off lists ofone or more non-limiting examples, instances, or illustrations.

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e., hardware) and any software and/orfirmware (“code”) that may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory (e.g., a volatileor non-volatile memory device, a general computer-readable medium, etc.)may comprise a first “circuit” when executing a first one or more linesof code and may comprise a second “circuit” when executing a second oneor more lines of code. Additionally, a circuit may comprise analogand/or digital circuitry. Such circuitry may, for example, operate onanalog and/or digital signals. It should be understood that a circuitmay be in a single device or chip, on a single motherboard, in a singlechassis, in a plurality of enclosures at a single geographical location,in a plurality of enclosures distributed over a plurality ofgeographical locations, etc. Similarly, the term “module” may, forexample, refer to a physical electronic components (i.e., hardware) andany software and/or firmware (“code”) that may configure the hardware,be executed by the hardware, and or otherwise be associated with thehardware.

As utilized herein, circuitry is “operable” to perform a functionwhenever the circuitry comprises the necessary hardware and code (if anyis necessary) to perform the function, regardless of whether performanceof the function is disabled, or not enabled (e.g., by auser-configurable setting, factory setting or trim, etc.).

As utilized herein, “and/or” means any one or more of the items in thelist joined by “and/or”. As an example, “x and/or y” means any elementof the three-element set {(x), (y), (x, y)}. That is, “x and/or y” means“one or both of x and y.” As another example, “x, y, and/or z” means anyelement of the seven-element set {(x), (y), (z), (x, y), (x, z), (y, z),(x, y, z)}. That is, “x, y, and/or x” means “one or more of x, y, andz.” As utilized herein, the terms “e.g.,” and “for example,”“exemplary,” and the like set off lists of or provide one or morenon-limiting examples, instances, or illustrations.

The terminology used herein is for the purpose of describing particularexamples only and is not intended to be limiting of the disclosure. Asused herein, the singular forms are intended to include the plural formsas well, unless the context clearly indicates otherwise. It will befurther understood that the terms “comprises,” “includes,” “comprising,”“including,” “has,” “have,” “having,” and the like when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another element. Thus, for example, a first element, afirst component or a first section discussed below could be termed asecond element, a second component or a second section without departingfrom the teachings of the present disclosure. Similarly, various spatialterms, such as “upper,” “lower,” “side,” and the like, may be used indistinguishing one element from another element in a relative manner. Itshould be understood, however, that components may be oriented indifferent manners, for example an electronic device may be turnedsideways so that its “top” surface is facing horizontally and its “side”surface is facing vertically, without departing from the teachings ofthe present disclosure.

The drawings are of illustrative embodiments. They do not illustrate allembodiments. Other embodiments may be used in addition to or instead ofthe illustrative embodiments. Details that may be apparent orunnecessary may be omitted to save space or for more effectiveillustration. Some embodiments may be practiced with additionalcomponents or steps and/or without all of the components or steps thatare illustrated.

Some embodiments according to the present disclosure provide, forexample, suitable logic, circuitry, code, and/or combinations thereofthat may be adapted to perform the functions or acts described herein.

Some embodiments according to the present disclosure may relate to, forexample, systems and methods that provide an active cover for anelectronic device or equipment. Some embodiments contemplate that theactive cover and the electronic device or equipment can communicate(e.g., digitally communicate) with each other. Some embodimentscontemplate that the active cover and the electronic device or equipmentcan power themselves, for example, via direct current (DC) powersupplies (e.g., rechargeable batteries) and/or via alternating current(AC) power supplies (e.g., wall outlets). Some embodiments furthercontemplate that one or both of the active cover and the electronicdevice or equipment can power and/or recharge the other.

Some embodiments according to the present disclosure provide that theactive cover can sense when the electronic device is generating an alertor receiving a message, a notification, a call, an email, and/or anindication, and can provide an enhanced alert or indication (e.g.,audible and/or visual alert or indication) instead of or in addition tothe generated alert or indication of the electronic device. The activecover can provide a visual display (e.g., patterns of lights, animatedicons, animated emojis, lightshows, scrolling text, video, etc.),display information (e.g., a message, a notification, and/or anindication) received from the electronic device on a graphical userinterface (e.g., a touch-sensitive screen), generate a sound (e.g.,voice, musical note, audible tone, etc.), and/or vibrate.

Some embodiments according to the present disclosure contemplate thatthe active cover includes a mobile device cover for use with, forexample, a host mobile device (e.g., a cellular handset, a cellulardevice, a smartphone, a wireless phone, a wireless device, a wirelesshandset, a multimode phone, a mobile phone compliant with multiplewireless communication standards, a mobile phone equipped with a globalpositioning system, a multiple-input-multiple-output phone, a wirelesscommunication device, a two-way radio, a communication device with oneor more antennas, etc.). The systems and methods disclosed herein canalso be used with, for example, tablets, tablet computers, laptops,computers, computing devices, and other devices as well. The systems andmethods can be used with stationary devices such as, for example,desktop computers and stationary monitors and/or displays as well. Someembodiments according to the present disclosure that the functionalityof the active cover can be directly implemented into the host mobiledevice, for example, as part of the housing of the host mobile device.

Some embodiments according to the present disclosure contemplate that,during a host mobile device alert or event, an active mobile devicecover can provide its own alert or indication according to signals(e.g., alert signals, indication signals, data, digital signals, etc.)received from the host mobile device. The active mobile device cover mayalso light in a distinct or random pattern such as, for example, anyarrangement, sequence, etc. using one or more lights (e.g., illuminatingdevices, display devices, lighting devices, light emitting diodes(LEDs), liquid crystal displays (LCDs), etc.) in which different colors,brightness, intensities, etc. form shapes, images, icons, emojis, text,alphanumeric text, video, messages, notifications, etc. that are eitherstatic or moving (e.g., animated), for example. The lights may beindividual or distinct lighting devices or may be part of or form atleast a portion of a screen or a display of the active mobile devicecover. In some embodiments, the distinct or random patterns can beilluminated according to the sound, sound signal, alert data, digitalsignal, caller, contact, notification, etc., and/or other informationgenerated by the host mobile device, and received by the active mobiledevice cover, for example. In some embodiments, a distinct pattern canbe assigned (e.g., manually by a user or automatically) to an associatedsound, sound signal, alert, alert signal, digital signal, and/or otherinformation. For example, a distinct pattern can be assigned to aparticular ring tone, ring tone signal, contact information (e.g.,telephone number, email address, etc.), etc. A random pattern can beassigned to and/or associated with particular sounds, sound signals,alerts, alert signals, digital signals, callers, contacts,notifications, etc., and/or other information. For example, a randompattern or selected pattern can be assigned to a particular ring tone orring tone signal of the host mobile device, or to a particular source(e.g., telephone number, caller ID, email address, IP address, etc.) ofa message, email, call, etc. The random pattern can also be assigned tounassigned identifiers (e.g., telephone numbers, email addresses, IPaddresses, source identifiers, etc.) or unrecognized and/or unknownidentifiers. In addition to enhancing the look and feel of the outsideof the host mobile device, the active mobile device cover provides theuser with superior sensory input over the host mobile device alone,and/or protect the host mobile device from drops, scratches, etc.

Some embodiments according to the present disclosure provide a mobiledevice cover with lights such as light emitting diodes (LEDs) which canbe part of and/or form different types of displays (e.g., organic LED(OLED) screens, RGB LED screens, LCD displays, LED indicator lights,touch-sensitive displays, screens, etc.), or other light sources ordisplays.

Some embodiments according to the present disclosure provide a mobileapplication that runs on a host mobile device. The mobile applicationprovides a graphical user interface including one or more graphicalelements that are used to control the mobile device cover and the hostmobile device.

FIG. 1A shows an exemplary mobile device cover 100 according to anembodiment of the present disclosure. As shown in FIG. 1A, the mobiledevice cover 100 (e.g., a cover, a case, a shell, a protector, etc.) isphysically and/or electrically connected to a host mobile device 110. Insome embodiments, the mobile device cover 100 is wirelessly connected tothe host mobile device 110. In some embodiments according to the presentdisclosure, the host mobile device 110 (not shown in FIG. 1A except fora camera 125 and a sensor 135 on a back side 185 of the host mobiledevice 110) may be slipped inside or inserted into the mobile devicecover 100, or the mobile device cover 100 can be snapped on or stretchedaround, at least in part, or otherwise can be fit around, at least inpart, the host mobile device 110. FIGS. 1F and 1G show front sides of afront portion 145 and a middle portion 153 of the mobile device cover100 according to some embodiments of the present disclosure. Referringto FIGS. 1F and 1G, the host mobile device 110 (not shown) can beinserted or locked in between the guides 165 of the middle portion 153.Although some embodiments contemplate a via in the mobile device cover100 through which a female connector (e.g., a female USB-type connector)of the host mobile device can be accessed, other embodiments contemplatethe mobile device cover 100 with a connector 175 (e.g., a lightningconnector, a USB-type connector, a data connector, a rechargingconnector, multi-pin connector, etc.) that mates with the femaleconnector of the host mobile device 110 to provide a connection (e.g., apower connection, a physical connection, an electrical connection, asignal connection, a synchronization connection, etc.). In someembodiments, the connector 175 provides a connection (e.g., electricalconnection, data connection, etc.) between circuits in the host mobiledevice 110 and the mobile device cover 100. For example, the batteriesin the host mobile device 110 and the mobile device cover 100 can chargeeach other via the connector 175 and/or other ports, for example. Insome embodiments, the connector 175 is part of a connector assembly thatincludes a connector element 148, a coupler 149, and a port 147. Inaddition to or instead of the connector 175, the host mobile device 110and the mobile device cover 100 can communicate wirelessly (e.g.,Bluetooth communication, near field communication (NFC), other radiofrequency (RF) communication (e.g., Wi-Fi), infrared communication,etc.) with each other, as mentioned below. In some embodiments, thefront side 145 of the mobile device cover 100 can be interlocked withthe middle portion 153 of the mobile device cover 100 with the hostmobile device 110 there between. As noted before, the main display ofthe host mobile device 110 may or may not be covered by a transparentmaterial of the mobile device cover 100. In some embodiments, a window195 is provided in the front portion 145 of the mobile device cover 100so that the user can directly touch the display (e.g., touch-sensitivescreen) of the host mobile device 110.

In some embodiments, the mobile device cover 100 can be an accessory tothe host mobile device 110. In some embodiments, the mobile device cover100 can be an accessory that is operable while separate from the hostmobile device 110. The accessory can be in wireless communication withthe host mobile device 110. In some embodiments, the mobile device cover100 and the host mobile device 110 can be controlled via inputs (e.g.,buttons, touch-sensitive screens, capacitive touch, sliders, graphicalelements on graphical user interfaces, etc.) located on the mobiledevice cover 100, the host mobile device 110, a mobile applicationrunning on the host mobile device 110, a mobile application running onthe mobile device case 100, a wired and/or wireless signal sent to thehost mobile device 110, a wired and/or wireless signal sent to themobile device cover 100, etc. The wireless signal can include, forexample, Bluetooth signals, IEEE 802.11 signals, wireless local areanetwork (WLAN) signals, wireless personal area network (PAN) signals,Zigbee signals, infrared signals, RF signals, etc. sent to the mobiledevice cover 100, the host mobile device 110, etc. Accordingly, themobile device cover 100 and/or the host mobile device 110 include, forexample, antennas and circuits (e.g., processors, wireless hardware,transceivers, transmitters, receivers, etc.) to support wirelesscommunication between them 100, 110, and/or between the mobile devicecover 100, the host mobile device 110, and/or other wireless devices(e.g., wireless speakers, wireless microphones, wireless headphones,wireless earbuds, wireless displays, base stations, access points,wireless networks, etc.).

Referring to FIG. 1A, a back side 158 of the back portion 155 (e.g.,back cover) of an exemplary mobile device cover 100 according to anembodiment of the present disclosure is shown. The back portion 155 ofthe mobile device cover 100 has lights 160. The lights 160 can form, bea part of, and/or illuminate a screen (e.g., a main screen or display,indicator lights, light patterns, etc.) and can emit different colorswith different intensities at different times. The lights 160 can alsoform, be a part of, and/or illuminate another screen 132 or an extensionof the main screen along an edge 130 (e.g., a beveled edge, a chamferededge, a side, a lateral side, a border of the screen 162, etc.) of themobile device cover 100. Further, the lights 160 can illuminate beads180 with different colors as indicator lights, for example. The beads180 can be colored or not, and can be at least partially transparent,for example. In some instances, the beads 180 can take the configurationof letters, numbers, and/or shapes and can be flat or raised instructure. The beads 180 can be used as part of a Braille reader system,for example. In some instances, the beads 180 can include, for example,LED or light covers. In some examples, the beads 180 can be flattransparent plastic windows that can be positioned over lights 160. Insuch an instance, the beads 180 can be colored, and/or the lights 160can provide color through colorless, transparent beads 180. In someembodiments, the beads 180 can be disposed throughout the back cover 155of the mobile device cover 100 so that the beads 180 can be illuminatedin particular colors, patterns, and/or intensities at particular timesand/or in response to certain alerts or other information (e.g., digitalsignals, digital data, analog signals, etc.) received from the hostmobile device 110.

In some embodiments, when the host mobile device 110 and the mobiledevice cover 100 are operatively coupled, the mobile device cover 100can provide indicators and/or data (e.g., digital data, video data,streaming data, etc.) from the host mobile device 110 to the user viaoutput interfaces (e.g., lights, screens, speakers, etc.) of the mobiledevice cover 100. In some embodiments, when the host mobile device 110and the mobile device cover 100 are operatively coupled, the mobiledevice cover 100 and the host mobile device 110 are in one- or two-waydigital and/or analog data communication. The mobile device cover 100can display information, data, and/or content (e.g., multimedia content,video content, streaming content, social media content, scrolling text,etc.) received from the host mobile device 110. Further, the host mobiledevice 110 can display information, data, and/or content received fromthe mobile device cover 100. The host mobile device 110 and/or themobile device cover 100 can cause information, data, and/or content tobe displayed on the host mobile device 110. Further, the host mobiledevice 110 and/or the mobile device cover 100 can cause information,data, and/or content to be displayed on the mobile device cover 100. Theinformation, data, and/or content can be received from the host mobiledevice 110, the mobile device cover 100, another device, and/or a thirdparty, such as a mobile application, a website, etc. FIG. 1E shows anembodiment of the mobile device cover 100 in which the back cover 1030includes the lights 160 forming a touch-screen display 162 that can besimilar or the same as the display that can be shown on the main displayof the host mobile device 110. Thus, for example, the touch-screendisplay 162 of the mobile device cover 100 can operate in a same orsimilar manner (e.g., same or similar graphical user interface,graphical elements, touch-and-feel, etc.) as the main display of thehost mobile device 110. The touch-screen display 162 of the mobiledevice cover 100 can provide the same or similar array of icons 164 asthe main display of the host mobile device 110, for example, or can becompletely different. This can be useful, for example, if the display ofthe host mobile device 110 is being used for another purpose (e.g.,playing a video, taking a call, work use, personal use, etc.), but theuser wants to access other mobile applications. For example, the hostmobile device 110 can be used to operate a GPS navigation application,while the mobile device cover 100 is being used to watch a movie or tostream video. Further, since the host mobile device 110 and the mobiledevice cover 100 can be in wireless communication, the mobile devicecover 100 can be detached from the host mobile device 110 while watchingthe movie or streaming video, for example.

Referring to FIG. 1A, when the host mobile device 110 is receiving anincoming call, for example, beads 180 that form the word “CALL” on theback cover 155 of the mobile device cover 100 can be illuminated, causedto flicker, flash, etc. If a calendar event notification is activated orreceived by the host mobile device 110, for example, the beads 180 thatform the word “ALERT” can be illuminated, caused to flicker, flash, etc.If a text message is received by the host mobile device 110, forexample, the beads 180 that form the word “TEXT” can be illuminated,caused to flicker, flash, etc. These events and others (e.g., socialmedia postings or messages, changes in sports scores, news items,emails, SMS messages, etc.) can also be displayed on the touch-screendisplay 162. The beads 180 can also be illuminated different colors andwith different intensities to indicate different degrees of urgency. Forexample, if the alert is urgent (e.g., an email sent with “highimportance”), the beads 180 that form the word “ALERT” can flash redand/or with increased intensity to indicate urgency. In another example,if the incoming call or text message is not from an important person,which can be designated via programming, user settings, userconfigurations, user preferences, etc., the corresponding beads 180 canbe illuminated a dim blue. In some embodiments, the mobile device cover100 can determine the identity of the caller or the message sender viaelectrical signals, sound signals, acoustic signals, wireless signals,digital signals, etc. received from the host mobile device 110. In someembodiments, the host mobile device 110 can determine the identity ofthe caller or the message sender and send a data signal corresponding toand/or identifying the caller or the message sender to the mobile devicecover 100 as well as other information (e.g., voice mail, text message,indications of importance, etc.). Further, the user may be notified asto the name, number, email address, etc. of the sender or source of thealert, text, email, or other notification via the lights 160, beads 180,or other output devices (e.g., speakers, screens, vibration, etc.) ofthe mobile device cover 100.

In some embodiments, the mobile device cover 100 can be configured toprovide video (e.g., live streaming video, streaming video, storedvideo, etc.) and/or other information (e.g., digital data, messages,news, alerts, etc.) on one or more screens. The video can be providedvia the host mobile device 110, for example, or some other source towhich the mobile device cover 100 and/or the host mobile device 110 isoperatively coupled. For example, the mobile device cover 100 can haveits own wireless link with an access point (e.g., an IEEE802.11-compliant access point) or a base station (e.g., a cellular basestation, a portable base station, etc.) from which to download mediacontent. The mobile device cover 100 can also include memory storage(e.g., non-transitory memory storage, solid state memory storage,removable memory sticks, disks, cards, etc.) on which resides mediacontent for playing or displaying on the screen of the mobile devicecover 100 and/or the host mobile device 110. The video can be, forexample, stored on the host mobile device 110 or can be streamed via awireless link (e.g., cellular link, WIFI link, IEEE 802.11 link,wireless local area network (WLAN) link, Bluetooth link, RF link, etc.)with a content provider or a third party application. In someembodiments, closed captioning or subtitles can scroll along the mainscreen 162 which can include and/or be supplemented with one or morescreens 132 on one or more edges 130 of the mobile device cover 100. Insome embodiments, the mobile device cover 100 can be configured toprovide an alert of a received video message and to play the videomessage on the screen 162 of the mobile device cover 100. The screen 162of the mobile device cover 100 can be substantially independent or cansubstantially mirror the screen of the host mobile device 110. Thescreens 162, 132 can be incorporated into the housing of the electronicdevice. Further, the screen 162 of the mobile device cover 100 can betouch-sensitive and employ graphical elements of a graphical userinterface. Thus, for example, a user input via the touch-sensitivescreen 162 of the mobile device cover 100 can provide a user input tothe host mobile device 110 and/or the mobile device cover 100. Thescreen of the mobile device cover 100 can be set up to substantiallymirror the screen of the host mobile device 110 or to operateindependently of the screen of the host mobile device 110. Content ormaterial can also be displayed on the mobile device cover 100 and/or thehost mobile device 110 that is from an application on the host mobiledevice 110, for example. For example, if the user has access to a sportsapplication running on the host mobile device 110 that shows sportsvideos, television channels, movie channels, or live events on the hostmobile device 110, the video may be displayed on the host mobile device110 and/or the mobile device cover 100.

Some embodiments provide that digital signals can be received orprovided by the host mobile device 110 and forwarded to the mobiledevice cover 100 for storage, processing, and/or output (e.g., on adisplay, lights, a speaker, a vibrating mechanism, etc.). For example,in addition to multimedia data, some embodiments provide that data(e.g., alphanumeric data, indicators, control data, source information,etc.) can be received or provided by the host mobile device 110 andforwarded to the mobile device cover 100 for storage, processing, and/oroutput. For example, the edge screen 132 (or any other screen or displaycomprising lights 160 on the mobile device cover 100) can be configuredto scroll information relating to news, sports, live or recorded eventsor movies, stocks, weather, calendar events, text messages, alerts,email, social media messages (e.g., messages or posts from mobileapplications or websites such as Facebook, Twitter, Snapchat, Instagram,etc.), etc. In some embodiments, the information can scroll around oneor more edge screens 132 around the mobile device cover 100. In someembodiments, the host mobile device 110 can be set to periodicallyreceive or retrieve sports data (e.g., scores, news items, etc.) orother types of data. The data can be from, for example, websites, mobileapplications, other host mobile devices, etc. The host mobile device 110can send sports data, for example, to the mobile device cover 100; andthe mobile device cover 100 can display or scroll the data across theedge screen 132 of the mobile device cover 100 or display or scroll onthe screen 162. In some embodiments, the edge screen 132 can betouch-sensitive, thereby allowing the user to tap or swipe an emailnotification and read a scrolling email on the edge screen 132 or onanother display (e.g., the main display 162 on the back cover 155) ofthe mobile device cover 100. In some embodiments, the data can flowacross the edge screen 132 in response to a finger sweeping motion alongthe edge touch-sensitive screen 132. In one embodiment, an incoming textmessage can be indicated by the beads 180 forming the word “TEXT” beingilluminated by lights 160, the sender of the incoming text can bedisplayed on the edge screen 132, and the text of the text message canbe displayed on the main screen 162 on the back cover 155 of the mobiledevice cover 100. In one embodiment, alphanumeric letters are displayedon the screen on the back cover 155 and the edge 130, eithersimultaneously or independently, indicating that a text message has beenreceived and possibly displaying the sender's name, the sender'sassociated icon (e.g., icon, emoji, animated icon, animated emoji,etc.), the sender's associated image (e.g., sender's picture), thesender's subject, the sender's header, the sender's body text, thesender's partial or full text, etc. A text or email icon can bedisplayed instead of the words TEXT, for example. The display can alsobe a series of LEDs forming a grid to accommodate lights show, scrollingtext, etc.

The edge screen 132 can be configured to scroll completely or partiallyaround the mobile device cover 100 and/or along one or more of its edges130. In some embodiments, the edge 130 can be segmented or partitionedso that the right edge portion is reserved for a first subject (e.g.,stocks), the left edge portion is reserved for a second subject (e.g.,sports), the bottom edge portion is reserved for a third subject (e.g.,email), and the top edge portion is reserved for a fourth subject (e.g.,calendar items, alerts, etc.), for example. Within each segment, theedge screen 132 can scroll the data. In some embodiments, the user canprogram and/or select which subject is displayed on each individualsegment on the mobile device cover 100. In some embodiments, the usercan program the mobile device cover 100 so that it decides on whichsegment to display a particular subject (e.g., incoming call, incomingtext, incoming email, incoming message, mobile device notification,mobile device accessory notifications, music or other audionotifications, social media notifications, etc.).

FIG. 1B shows a top view of an exemplary mobile device cover 100according to an embodiment of the present disclosure. FIG. 1C shows apartially exploded side perspective view of an exemplary mobile devicecover 100 according to an embodiment of the present disclosure.

Referring to FIGS. 1B and 1C, the mobile device cover 100 can beadapted, for example, to provide physical vias (e.g., access openingsand windows) through which various input interfaces and outputinterfaces of the host mobile device 110 can be accessed withoutdetaching the mobile device cover 100 from the host mobile device 110.In some embodiments, the mobile device cover 100 may provide a physicalopening to access a display, a camera, a button, a control, otherinput/output (I/O) interfaces, etc. of the host mobile device 110. Insome embodiments, the mobile device cover 100 does not cover the maindisplay of the host mobile device 110 when the mobile device cover 110is attached to the host mobile device 110. In some embodiments, themobile device cover 100 may provide a transparent or partiallytransparent cover portion, for example, over a display or other portionsof the host mobile device 110. The transparent cover portion can be madeof materials that, for example, do not interfere with the operation ofany of the touch screens, speakers, and/or buttons of the host mobiledevice 110. In some embodiments, the materials can be substantiallytransparent to wireless communication links used by the host mobiledevice 110 and/or the mobile device cover 100. The transparent coverportion may also protect areas of the host mobile device 110 such astouch screens from scratches or other damage.

Some embodiments according to the present disclosure may provide thatthe mobile device cover 100 is made of one or more of the followingmaterials: silicone, rubber, metal, plastic, polymers, polycarbonate,composites, cloth, metal, wood, acrylic, glass, plexiglass, and/or othermaterials. The cover material may be, at least in part, opaque ortransparent. The cover material may assist a user in gripping the hostmobile device 110 and may protect the host mobile device 110. The covermaterial may be, for example, one or more of the following: shockresistant, shock proof, shatter proof, shatter resistant, dustresistant, dust proof, water resistant, water proof, etc. In someembodiments, the mobile device cover 100 may be made up of multiplepieces (e.g., portions 100 a, 100 b, 100 c, one or more printed circuitboards, housings, etc.), as shown in FIGS. 1B and 1C. In someembodiments, the multiple pieces of the mobile device cover 100interlock together to house, become the back panel of the host mobiledevice 110, and/or to connect (e.g., physically and/or electricallyconnect, snap, interlock, etc.) to the host mobile device 110.

Referring to FIGS. 1B and 1C, the mobile device cover 100 can include,for example, circuitry 150 and lights 160 disposed on one or moreprinted circuit boards. In some embodiments, the circuitry 150 caninclude one or more of the following: one or more processors, one ormore non-transitory memories, signal processors, light controlcircuitry, light drive circuitry, battery recharging circuitry, batterycontrol circuitry, display control circuitry, sensors, input interfacecircuitry, output interface circuitry, digital-to-analog converters,analog-to-digital converters, wired transceivers, wireless transceivers,input/output ports, input/output interfaces, and antennas. The one ormore non-transitory memories can be configured to store, for example,data (e.g., input data, data received from the host mobile device 110,stored reference data, stored configuration data, stored personal data,etc.) and processor-executable instructions or code for use with the oneor more processors. The circuitry 150 can be connected, for example, toand/or can include the lights 160. Some embodiments provide that thelights can include one or more of the following: LEDs, flexibleactive-matrix OLEDs (AMOLEDs), OLEDs, phosphor-based LEDs, white LEDs(WLEDs), multi-color WLEDs, semiconductor LEDs, other types of LEDs,LCDs, LCD touch screens, electroluminescence, pixel displays, etc., andcan be arranged or used in a specific pattern, array, sequence, etc.Some embodiments provide that the lights can be raised or provide bumpysurfaces suitable for use in a Braille system. Various components and/orelements of the circuitry 150 can be connected to each other through oneor more buses, for example.

The mobile device cover 100 can also include, for example, a battery 170(e.g., a rechargeable battery) that can be used to power, for example,the circuitry 150, the lights 160, and any other circuitry or componentsin the mobile device cover 100 and/or the host mobile device 110. Thebattery 170 can also be used to power the host mobile device 110 and/orto recharge a battery in the host mobile device 110. In someembodiments, the mobile device cover 100 does not have a battery andinstead can be powered by the host mobile device 110. Some embodimentsaccording to the present disclosure provide that the battery 170 can berechargeable or not rechargeable. If not rechargeable, the battery 170can be replaced. Some embodiments of the battery 170 include, forexample, a lithium battery, an alkaline battery, a silver-oxide battery,nickel cadmium battery, nickel metal hydride battery, lithium ionbattery, lithium ion polymer battery, etc. If rechargeable, then thebattery 170 can be recharged, for example, by drawing energy from one ormore interfaces of the host mobile device 110 (e.g., an audio port, anearphone jack, a docking port (e.g., a USB-type port, a lightningconnector port, a power and signaling connection port, etc.), a wirelesscharging pad, etc.). The battery 170 can also be recharged by drawingenergy separate from or independent of the host mobile device 110.Similarly, a rechargeable battery of the host mobile device 110 can becharged through one or more interfaces of the host mobile device 110that are electrically or wirelessly connected to the mobile device cover100. The rechargeable battery of the host mobile device 110 can also berecharged by drawing energy separate from or independent of the hostmobile device 110.

For example, independent of whether the mobile device cover 100 isconnected to the host mobile device 110, the mobile device cover 100 canbe separately plugged into a wall outlet or wirelessly charged at awireless charging station. The mobile device cover 100 can also becharged by plugging it into a computer, a charger bank, a generator,etc. via a USB-type connection, for example. The battery 170 of themobile device cover 100 can be charged by a piezoelectric batterycharger, for example. In some embodiments, the piezoelectric batterycharger can convert force (e.g., caused by pressure, movements,mechanical forces, etc.) into electrical energy for use by the battery170. Some embodiments contemplate converting other types of energy(e.g., sound energy, light energy, electromagnetic energy, magneticenergy, thermal energy, moving air, wireless energy, etc.) intoelectrical energy to charge the battery 170. In some embodiments, themobile device cover 100 can utilize charging methods such as conductiveand inductive charging.

In some embodiments, the battery 170 of the mobile device cover 100 canalso be recharged when the host mobile device 110 is wirelessly orwiredly connected to a power source (e.g., AC and/or DC power source).For example, the battery 170 of the mobile device cover 100 can berecharged when the host mobile device 110 is connected to a wall outlet,for example, such as when a docking port of the host mobile device 110is connected to a wall outlet. The battery 170 may receive energydirectly from the wall outlet (e.g., via connecting the mobile devicecover 100 directly to the wall outlet) or indirectly from the walloutlet through the host mobile device 110. In addition, the battery 170may receive energy when a docking port or some other interface of thehost mobile device 110 is connected to a computer while electrically orwirelessly connected to the mobile device cover 100. Some embodimentsaccording to the present disclosure contemplate that the circuitry 150receives power from the host mobile device 110 without using the battery170 or in combination with the battery 170. Thus, some embodimentsaccording to the present disclosure might not have a dedicated batteryas part of the mobile device cover 100, or might use the battery 170 asa back-up power source.

In some embodiments, just as the battery 170 of the mobile device cover100 can draw on energy from the host mobile device 110, the battery ofthe host mobile device 110 can draw on energy from the mobile devicecover 100 to recharge the battery of the host mobile device 110 or tosupplement power to the host mobile device 110. For example, asrechargeable batteries age, they are less capable of fully powering themain processor on the host mobile device 110. The aging batteries havereduced full charge capacity and provide less power, voltage, and/orcurrent during normal operation. As a result, some processors (e.g.,central processor, graphics processor, general processor, dedicateprocessor, etc.) will enter a power-save mode in which processor speed(e.g., clock speed) and/or load capacity (e.g., peak load) are reducedto conserve power and/or energy which is detrimental to performanceand/or inconvenient to the user. In such a situation, the host mobiledevice 110 can supplement the power and capacity of its own battery withthe battery 170 of the mobile device cover 100, thereby avoiding thepower-save mode of the processor of the host mobile device 110 or viceversa. Accordingly, the processors in the host mobile device 110 cancontinue to operate at normal operation speeds and load capacities.Further, by supplementing power and capacity of the host mobile device100, the battery 170 of the mobile device cover and the battery of thehost mobile device 110 can be used to power a turbo mode in theprocessor of the host mobile device 110 or vice versa. For example, inturbo mode, the processor (e.g., a central processor, a graphicsprocessor, a general processor, a dedicated processor, etc.) of the hostmobile device 110 can operate at one or more of the following: a highervoltage, a higher current, a higher power, a higher load capacity,and/or a higher clock speed than during normal operation. During turbomode, the host mobile device 110 and/or the mobile device cover 100 canoperate with greater performance and can perform moreprocessor-intensive applications.

In some embodiments, when the host mobile device 110 is electricallyconnected to the mobile device cover 100 (e.g., when the host mobiledevice 110 has been inserted into the mobile device cover 110) and themobile device cover 100 is plugged into a wall outlet, for example, thebattery 170 of the mobile device cover 100 and the battery of the hostmobile device 110 charge at the same time. In some embodiments, thebattery of the host mobile device 110 charges without a decrease incharge speed even when the host mobile device 110 and the mobile devicecover 100 are charged at the same time via the electrical connection(e.g., via a port 147) of the mobile device cover 100 to the wall plug,for example.

FIG. 1D shows an exploded side perspective view of an exemplary mobiledevice cover 100 according to an embodiment of the present disclosure.In some embodiments, the circuitry 150 can be embedded in the mobiledevice cover 100. In some embodiments, the circuitry 150 may include,for example, one or more circuit boards 150 a including, for example,one or more of the following: one or more processors, circuit elementsor components, an integrated circuit, an integrated circuit chip, asystem on a chip, etc. The circuitry 150 may also include, for example,one or more sensors 150 b (e.g., an audio sensor, a signal sensor, anoptical sensor, a wireless signal sensor, a wireless receiver, awireless transceiver, an electrical sensor, a power sensor, a batterysensor, an electromagnetic sensor, a vibration sensor, gyroscope sensor,iris scanner, fingerprint sensor, accelerometer, proximity sensor,barometer, hear rate sensor, a biometric sensor, etc.). Components 150 aand 150 b can be part of the same circuit board or can be part ofseparate circuit boards, for example, that are connected to form, inpart, the mobile device cover 100. A sensor can be part of components150 a, 150 b, or both. In some embodiments, the mobile device cover 100can include multiple circuit boards or multiple-layered circuit boards.

FIG. 2 illustrates an exemplary circuit arrangement according to anembodiment of the present disclosure. Referring to FIG. 2, a simplifiedblock diagram is shown of the circuitry 150. The circuitry 150 mayinclude one or more of the following: a processor 200, a memory 210, anI/O device 220, a bus 230, driver circuitry 240, and lights 160. Theprocessor 200, the memory 210, the I/O device 220, the driver circuitry240, and the lights 160 can be coupled to each other via one or morebuses 230. The circuitry 150 can include more or less than one processor200, one memory 210, one I/O device 220, one bus 230, one driver circuit240, and two lights 160 as illustrated in FIG. 2. Thus, some embodimentscontemplate employing different numbers of various elements of thecircuitry 150.

The driver circuitry 240 can include, for example, one or more of thefollowing: light drivers, LED drivers, shift registers, constant currentsupply, constant voltage supply, switching supply, FET amplifier, BJTamplifier, etc. In addition, some embodiments according to the presentdisclosure contemplate using a plurality of sensors, processors,memories, and/or driver circuits. Some embodiments provide that thedriver circuitry 240 can be part of the processor 200 and, in someembodiments, can take the place of the processor 200. Some embodimentsprovide that the driver circuitry 240 and other circuitry can beincorporated into a system on a chip (SOC). In some embodiments, thedriver circuitry 240 can be configured to control any amount orarrangement of similar or different lights 160, including a full display(e.g., a touch-sensitive screen, LED screen, etc.). In some embodiments,the driver circuitry 240 can be configured to power any number orarrangement of similar or different lights 160.

The I/O device 220 can include, for example, one or more of thefollowing: an input device (e.g., a button), a touch-screen display, awired and/or wireless transceiver (e.g., cellular transceiver, Bluetoothtransceiver, WLAN transceiver, etc.), a wired and/or wirelesstransmitter, a wired and/or wireless receiver, an antenna, a speaker, amicrophone, an I/O port (e.g., earbud port, earphone port, microphoneport, speaker port, etc.), an I/O interface, data connector port, powerconnector port, wired and/or wireless communication device, GPSreceiver, a network interface, etc.

The processor 200 can include, for example, one or more of thefollowing: a general processor, a central processing unit, a digitalfilter, a microprocessor, a digital processor, a digital signalprocessor, a microcontroller, a programmable array logic device, acomplex programmable logic device, a field-programmable gate array andan application specific integrated circuit (ASIC), and a memory (e.g., acache). Code, instructions, software, firmware, and/or data including,for example, a mobile application may be processed and/or executed bythe processor 200 to perform any of the operations, functions, and/orfeatures described in the present disclosure. Further, the code,instructions, software, firmware, and/or data including, for example,the mobile application may be stored in the processor 200 and/or thememory 210. The code, instructions, software, firmware, and/or data canbe automatically or manually updated, upgraded, modified, replaced,overwritten, supplemented, etc. via a wireless or wired connection.

The memory 210 can include, for example, one or more of the following: anon-transitory memory, a non-transitory processor readable medium, anon-transitory computer readable medium, a read only memory (ROM), arandom access memory (RAM), DRAM, EPROM, EEPROM, F-RAM, FIFO, NVRAM,SRAM, a cache, a semiconductor memory, a magnetic memory, an opticalmemory, a flash memory, a flash card, a compact flash card, memorycards, secure digital memory cards, a microcard, a minicard, anexpansion card, a smart card, a memory stick, a multimedia card, apicture card, flash storage, a subscriber identity module (SIM) card, ahard drive (HDD), a solid state drive (SSD), etc. The memory 210 may beconfigured to store code, instructions, software, firmware, and data foruse by the processor 200 and may be external, internal, or both withrespect to the processor 200. In some embodiments, the memory 210 alsostores a mobile application, settings, parameters, values, lightshows,icons (e.g., icons, emojis, graphical elements, etc.), animations,scrolling text, etc. Further, the code, instructions, software,firmware, and/or data can be automatically or manually updated,upgraded, modified, replaced, overwritten, supplemented, etc. via awireless or wired connection.

FIGS. 26-41 show exemplary parts of an exemplary mobile device cover 100according to some embodiments of the present disclosure.

FIGS. 26-29 show different views of an exemplary middle frame 2600 ofthe mobile device cover 100 according to an embodiment of the presentdisclosure. For example, FIGS. 26-29 show a front view 2630, a back view2700, a side view 2800, and a perspective view 2900, respectively, ofthe middle frame 2600 of the mobile device cover 100 according to thepresent disclosure. The middle frame 2600 and other components of themobile device cover 100 can be made of, for example, one or more of thefollowing: plastic, metal, composite materials, alloys, wood, cloth,fibers, glass, plexiglass, resin, rubber, etc., and/or one or more othermaterials. Referring to FIGS. 26-29, the front of middle frame 2600 caninclude, for example, guides 2620 configured to receive the host mobiledevice 110 into a space 2640, and an opening 2630 configured toaccommodate the camera 125 and sensor 135 of the host mobile device 110when the host mobile device 110 is placed in the space 2640 provided bythe middle frame 2600. The back of the middle frame 2600 can alsoprovide a space 2710 to accommodate a rechargeable battery 170 in whichthe space is delineated by guides 2730. The guides 2730 can include, forexample, screw posts 2740 for receiving screws that are used to mountone or more printed screen boards. In addition, the middle frame 2600provides a space 2720 to receive connector or port components and/orcircuitry (e.g., connector element 148, coupler 149, port 147, wires,and other circuitry). The middle frame 2600 can also include, forexample, a locking mechanism 2910 that can be integral with the guides2620 and configured to lock with a locking mechanism 3310 of a frontframe 3000 when the middle frame 2600 and the front frame 3000 areassembled. The locking mechanism 2910 of the middle frame 2600 can alsobe configured to lock with a locking mechanism of a back frame 3400.Some embodiments also contemplate that one or more of the front frame3000, the middle frame 2600, and/or the back frame 3400 can be integralwith or incorporated into the host mobile device 110.

FIGS. 30-33 show different views of an exemplary front frame 3000 of themobile device cover 100 according to an embodiment of the presentdisclosure. For example, FIGS. 30-33 show a front view 3010, a back view3100, a side view 3200, and a perspective view 3300, respectively, ofthe front frame 3000 according to the present disclosure. The frontframe 3000 and other components of the mobile device cover 100 can bemade of, for example, one or more of the following: plastic, metal,composite materials, alloys, wood, cloth, fibers, glass, plexiglass,resin, rubber, etc., and/or one or more other materials. In oneembodiment, the front frame 300 is made up of rubber to provide shockabsorption and/or vibration resistance. Further, a front frame 300 madeup of rubber is also flexible for securely and easily attaching andremoving the front frame 3000 to the middle frame 2600. In someinstances, the front frame 300 can be stretched around the middle frame2600 with the host mobile device 110 to attach or remove the front frame300 to or from the middle frame 2600. Referring to FIGS. 30-33, thefront frame 3000 can include, for example, an opening 3020 configured toprovide access to the main screen of the host mobile device 110, andbutton elements 3030. The button elements 3030 are configured to receivethe buttons of the host mobile device 110 and to provide buttons 3040 aspart of the mobile device cover 100 that, when pressed down by the user,press down the buttons of the host mobile device 110. The front frame3000 can also include, for example, a via 3110 that is configured toprovide access to a port and/or I/O device (e.g., a headphone port, anearphone port, a headset port, an I/O port, a speaker, a microphone, adock connector, a connector port, a USB-type port, etc.) of the hostmobile device 110. In some embodiments, the middle frame 2600 can alsoinclude, for example, a via that is configured to provide access to aport and/or I/O device (e.g., a headphone port, an earphone port, aheadset port, an I/O port, a speaker, a microphone, a dock connector, aconnector port, a USB-type port, etc.) of the host mobile device 110.The front frame 3000 can include, for example, a via 3210 that isconfigured to provide access to a switch 3210 (or some other user inputor output) of the host mobile device 110. The front frame 3000 alsoprovides a locking mechanism 3310 that is configured to lock with thelocking mechanism 2910 of the middle frame 2600 when the front frame3000 and the middle frame 2600 are assembled.

The front frame 3000 can also include, for example, a via 3110 oranother via that is configured to provide access to a port and/or I/Odevice (e.g., a headphone port, an earphone port, a headset port, an I/Oport, a speaker, a microphone, a dock connector, a connector port, aUSB-type port, etc.) of the mobile device cover 100. The earphone port(or headset port, headphone port, etc.) provided by the mobile devicecover 100 can be used by the host mobile device 110 when, for example,the host mobile device 110 no longer provides a dedicated earphone portor when its multi-purpose port is being used for some other purpose(e.g., charging the host mobile device 110). The host mobile device 110can use the ports of the mobile device cover 100, and the mobile devicecover 100 can use the ports of the host mobile device 110. Further, I/Odevices integrated with (or a part of) or connected to the host mobiledevice 110 can be used by the mobile device cover 100, and I/O devicesintegrated with (or a part of) or connected to the mobile device cover100 can be used by the host mobile device 110.

FIGS. 34-37 show different views of an exemplary back frame 3400 of themobile device cover 100 according to an embodiment of the presentdisclosure. For example, FIGS. 34-37 show a front view 3410, a back view3500, a side view 3600, and a perspective view 3700, respectively, ofthe back frame 3400 according to the present disclosure. The back frame3400 and other components of the mobile device cover 100 can be made of,for example, one or more of the following: plastic, metal, compositematerials, alloys, wood, cloth, fibers, glass, plexiglass, resin,rubber, etc., and/or one or more other materials. Referring to FIGS.34-37, the back frame 3400 can include, for example, an opening 3420configured to accommodate the camera 125 and sensor 135 of the hostmobile device 110 when the host mobile device 110 is placed in the space2650 provided by the middle frame 2600 and the back frame 3400 issecured or locked onto the middle frame 2600. In some embodiments, theback frame 3400 can be unlocked, removed, and replaced with another backframes 3400 with the same or different appearance and/or functionality,for example. The back frame 3400 also includes, for example, a via 3430configured to receive a button structure 3800, and a via 3440 configuredto provide access to the port 147 of the mobile device cover 100 and/orthe host mobile device 110. The back frame 3400 is also structured toprovide a space 3510 to accommodate one or more printed circuit boardsthat can include, for example, one or more lights 160. In someembodiments, the back frame 3400 can be an integral part of a housing ofthe host mobile device 110.

FIGS. 38-41 show different views of an exemplary button structure 3800of the mobile device cover 100 according to an embodiment of the presentdisclosure. For example, FIGS. 38-41 show a front view 3810, a back view3900, a side view 4000, and a perspective view 4100, respectively, ofthe button structure 3800 according to the present disclosure. Thebutton structure 3800 and other components of the mobile device cover100 can be made of, for example, one or more of plastic, metal,composite materials, alloys, wood, cloth, fibers, glass, plexiglass,resin, rubber, etc. Referring to FIGS. 38-41, a front of the buttonstructure 3800 includes a push button 3820 that is in mechanicalcommunication with a spring return 3920. The sprint return 3920 includesa disc 3920 that comes nearer to and/or in contact with circuitry (e.g.,a magnetic sensor, a mechanical sensor, an electrical sensor, a switch,a relay, etc.) of a printed circuit board when the push button 3820 ispressed. The printed circuit can sense when the push button 3820 ispressed and/or released, and can determine the duration of the press,for example. The push button 3820 can be used to turn the mobile devicecover 100 on or off, and can be used as a single button control for themobile device cover 100 to turn on or off or modify notifications,operations, and modes (e.g., silent mode, flashlight mode, panic mode,etc.). The button structure 3800 is configured so that the button can beinserted through the via 3430 of the back frame 3400.

FIGS. 42-58 show an embodiment of an exemplary process for assembling amobile device cover 100 according to the present disclosure. FIG. 42shows a perspective view of a front side of the middle frame 2600. InFIG. 43, a cushion 4310 (e.g., a foam cushion, a rubber cushion, etc.)is secured (e.g., glued, fastened, etc.) in the space 2640 of the middleframe 2600 for receiving the host mobile device 110. The cushion 4310provides additional shock and/or vibration resistance or isolation andhelps to secure the host mobile device 110 in place. In FIG. 44, anexemplary host mobile device 110 is placed (e.g., inserted, slid, etc.)facing forward in the space 2640 of the middle frame 2600 such that theback of host mobile device 110 is disposed against the cushion 4310 andguided into place by guides 2630. In FIG. 45, the front frame 3000 ismounted on the middle frame 2600 over the host mobile device 110. Ifmade of rubber or other flexible material, the front frame 3000 isstretched over the middle frame 2600 and the host mobile 110. The frontframe 3000 and the middle frame 2600 are locked together by thestretched front frame 3000 and/or the mating of the locking mechanisms2910, 3310 of the front frame 3000 and the middle frame 2600.

The back view of the middle frame 2600 is shown in FIGS. 46-55 with thehost mobile device 110 already installed between the front frame 3000and the middle frame 2600. In FIGS. 46-48, a port connector 4610 (e.g.,a USB-type connector, a lighting connector, a serial connector, aparallel connector, etc.) is mounted on the middle frame 2600. The portconnector 4610 can provide, for example, a connection to the circuitry(including the battery 170) of the mobile device cover 100, a connectionto the host mobile device 110 (including its circuitry and battery),and/or a connection to an external device or power supply, for example.The port connector 4610 can be configured for male and/or femaleconnectors and includes port circuitry 4620. One or more screws 4710,4810 or another fastening mechanism (e.g., glue, fasteners, stakes,nails, etc.) is used to secure the port connector 4610 to the middleframe 2600 as shown in FIGS. 47 and 48.

In FIG. 49, the battery 170 (e.g., rechargeable battery) of the mobiledevice cover 100 is installed in the space 2710 of the middle frame2600. The battery 170 fits within guides 2730, some of which are alsoscrew posts 2740. In FIG. 50, battery wires 5010 are added forconnecting the battery 170 to the circuitry of the mobile device cover100. In FIG. 51, the port connector wires 5110 are added for connectingthe port connector 4610 including its circuitry 4620 to the rest of thecircuitry of the mobile device cover 100.

An exemplary printed circuit board 5210 is installed on the middle frame2600 of the mobile device cover 100. Referring to FIGS. 52-54, theprinted circuit board 5210 is mounted on the screw posts 2740 of themiddle frame 2600. The printed circuit board 5210 can include aplurality of printed circuit boards that are stacked and communicatewith each other via wires and other circuitry. Both sides of the printedcircuit boards can have circuitry. For example, the printed circuitboard 5210 shows an array of lights 160 that are can be controlled bycircuitry on the other side of the printed circuit board or by anotherprinted circuit board underneath the printed circuit board 5210, forexample. One or more screws 5310, 5410 or another fastening mechanism(e.g., glue, fasteners, stakes, nails, etc.) is used to secure theprinted circuit board 5210 to the middle frame 2600 as shown in FIGS. 53and 54. In FIG. 55, the button structure 3800 is installed such that thedisk 3920 of the spring return 3910 is over a sensor 5420 of the printedcircuit board 5210. The sensor 5420 is configured to sense when thebutton 3820 of the button structure 3800 is being pressed, held down,and/or released.

The back frame 3400 is mounted over the middle frame 2600 and covers theprinted circuit board 5210 as shown in FIG. 56. The back frame 3400 canbe clear, transparent, translucent, or semi-transparent. In someembodiments, the back frame 3400 is configured so that the array oflights 160 can shine through the back frame 3400. The back frame 3400 isdisposed so that the button 3820 of the button structure 3800 passesthrough the via 3430, and the opening 3420 accommodates the camera 125and sensor 135 of the host mobile device 110. Referring to FIG. 56, theback frame 3400 is secured to the middle frame 2600 via a lockingmechanism 5610 (e.g., ridges molded into the four sides of the middleframe 2600). The locking mechanism 5610 can be configured to permanentlyor removably secure, without damage, the back frame 3400 to the middleframe 2600. Other types of locking mechanisms 5610 (e.g., screws,fasteners, etc.) are within the scope of the present disclosure and canprovide easy removal of the back frame 3400 from the middle frame 2600.

FIGS. 57 and 58 show the assembly of the mobile device cover 100 in twoexploded views according to an embodiment of the present disclosure. Theprinted circuit board 5210 is shown in a simplified fashion and does notshow all of the circuitry on the one or more boards that make up theprinted circuit board 5210.

FIG. 76 shows an exemplary back frame 3400 that provides an exemplaryremovable plate (or removable portion) 3450 according to an embodimentof the present disclosure. Although shown as a plate, the removableportion of the back frame 3400 can be any shape, size, and/or material,and can include, for example, almost all of the backside 7610 of theback frame 3400. The plate 3450 can be removed and replaced with otherplates with different appearances (e.g., designs, prints, level oftransparency, colors, etc.), form factors (e.g., plate with diskextending from plate, shapes conducive for easy and secure handling,other shapes with or without the plate as a platform, etc.), and/ormaterials (e.g., metal, plastic, rubber, cloth, composite materials,alloys, etc.). The plate 3450 replacing the previous plate 3450 need notbe of the same shape, size, and/or material as illustrated by theinterchangeable removable plates (or removable portions) 3450 shown inFIGS. 77A-B.

FIGS. 79A-F show exemplary removable plates 3450 that areinterchangeable on the back frame 3400 of the mobile device cover 100and can enhance the design or appearance of the back frame 3400according to the present disclosure. FIGS. 79A-B show exemplaryremovable plates 3450 of different colors (e.g., blue color in FIG. 79Aand red color in FIG. 79B), or different levels of transparency (e.g.,25% transparency in FIG. 79A and 75% transparency in FIG. 79B). FIG. 79Cshows an exemplary removable plate 3450 with a college logo, forexample. FIG. 79D shows an exemplary removable plate 3450 with a sportsteam logo, for example. FIG. 79E-F show exemplary removable plates 3450with a customized message and/or a customized design. The plates can beslid or inserted into and/or mounted onto the back frame 3400. Further,the mobile application that runs on the host mobile device 110, forexample, that is used to configure the mobile device cover 100 can alsobe used to select different removable plates 3450 for purchase. Inaddition, a web site can be provided to select different removableplates 3450 for purchase. The mobile application and/or the web site canbe used to design removable plates 3450 with personalized text (e.g.,names, phrases, etc.) and/or graphics (e.g., icons, emojis, etc.) asshown in FIGS. 79E-F, for example. Once selected and/or designed, a usercan order (e.g., purchase) the removable plate 3450 for delivery or pickup. Some embodiments also provide for programming the mobile devicecover 100 to display the selected and/or customized designs through atransparent or semi-transparent back plate 3450 using lights 160 and/ora screen of the mobile device cover 100.

The plate 3450 can be removed and replaced with other plates thatprovide functionality and/or different functionality (e.g., a particulardisplay resolution, screen, speaker, microphone, projector, camera,flashlight, laser light, additional memory, additional processing power,etc.). The functionality, which can be accessed by the mobile devicecover 100 and/or the host mobile device 110, can be a new function orcan provided enhanced functionality over existing functionality of themobile device cover 100 and/or the host mobile device 110. For example,FIGS. 77A-B show side views of two exemplary removable plates (orremovable portions) 3450 of the back frame 3400 of the mobile devicecover 100 according to an embodiment of the present disclosure. Theremovable portion 3450 in FIG. 77A may be an existing plate 3450 of theback frame 3400, while the removable portion 3450 in FIG. 77B, which isinterchangeable with the existing plate 3450, can have a different look,design, color, and functionality. For example, the removable portion3450 in FIG. 77B can replace the plate 3450 in FIG. 77A on the backframe 3400 and can be used as a speaker and/or a microphone for use bythe mobile device cover 100 and/or the host mobile device 110. Theremovable portion 3450 need not be in physical contact with the backframe 3400 to function and may wireless communicate with the back frame3400. Thus, the removable portion 3450 can be separated from the backframe 3400 and operate as a wireless speaker.

The plate (or removable portion) 3450 can include, for example,circuitry 7710 within the plate housing 7720 as shown in FIG. 77B. Thecircuitry 7710 can be electrically connected and/or in wired and/orwireless communication with the rest of the circuitry of the mobiledevice cover 100. FIG. 78A shows an exemplary plate 3450 that housescircuitry 7710 and provides electrical contacts 7720 for connecting withthe rest of the circuitry of the mobile device cover 100 when the plate3450 is inserted into the back frame 3400. The edge of the plate 3450may be inserted into a female electrical connector of the back frame3400 which secures the plate 3450 in place. FIG. 78B shows anotherexemplary plate 3450 that houses circuitry 7710 and provides electricalcontacts 7720 for connecting with the rest of the circuitry of themobile device cover 100 when the plate 3450 is inserted into the backframe 3400. Contact can be made automatically when the plate 3450 isinserted into the back frame 3400. The electrical contacts 7720 can alsoinclude, for example, a magnet for securing the plate 3450 to the backplate 3400 and maintaining contact between the electrical contact 7720and a corresponding electrical contact of the back frame 3400.

FIGS. 80A-B show two exemplary embodiments of interchangeable backframes 3400 of the mobile device cover 100 according to the presentdisclosure. Instead of or in addition to replacing a removable plate3450, some embodiments provide for interchangeable back frames 3400.Thus, similar to the discussion with respect to interchangeable backplates 3450, a back frame 3400 can be removed and replaced by anotherback frame 3400 that provides a different size, shape, material, and/orfunctionality, for example. The back frame 3400 in FIG. 80A can beremoved from the mobile device cover 100 and replaced with the backframe 3400 in FIG. 80B to provide, among other things, one or more touchscreens 8010. The back frame 3400 can house circuitry to support thefunctionality of the interchangeable back frame and to facilitateelectrically connecting and/or communicating wiredly and/or wirelesslywith the rest of the circuitry of the mobile device cover 100. Just aswith the back plates 3450, back frames 3400 can be selected, designed,and/or ordered using a mobile application and/or a website for pickup ordelivery to the customer.

FIG. 81 shows an exemplary embodiment of a host mobile device 110 withan interchangeable back cover 8110 according to the present disclosure.Referring to FIG. 81, the back cover 8110 of the host mobile device 110can be replaced with another back cover 8110. Similar to discussionswith respect to the removable plate 3450 and the interchangeable backframes 3400 of the mobile device cover 100, a back cover 8110 of thehost mobile device 110 can be removed and replaced by another back cover8110 that provides a different size, shape, material, and/orfunctionality, for example. The back cover 8110 of the host mobiledevice 110 in FIG. 81 can be removed from the host mobile device 110 andreplaced with another back cover 8110 to provide, among other things,the functionality of one or more touch screens 8120 for the back of thehost mobile device 110 (in addition to the main screen on the front ofthe host mobile device 110). The back cover 8110 can house circuitry tosupport the functionality of the interchangeable back cover 8110 and tofacilitate electrically connecting and/or communicating wiredly and/orwirelessly with the rest of the circuitry of the host mobile device 110.Just as with the back plates 3450 and back frames 3400 of the mobiledevice cover 100, the back cover 8110 of the host mobile device 110 canbe selected, designed, and/or ordered using a mobile application and/ora website for pickup or delivery to the customer.

FIGS. 59-70 show some exemplary circuits that are part of the printedcircuit board 5210 and other circuitry of the mobile device cover 100according to the present disclosure.

FIG. 59 shows an exemplary USB-to-lightning-connector circuit 5900 ofthe mobile device cover 100 according to an embodiment of the presentdisclosure. The circuit 5900 includes a male lightning connector 5910, aswitch 5930, and a USB-type receptacle 5920. The male lightningconnector 5910 is inserted into a female lightning connector of the hostmobile device 110 when the host mobile device 110 is placed into themiddle frame 2600. The USB-type receptacle 5920 includes, for example, afemale micro-USB connector that is part of the mobile device cover 100.An embodiment of the female micro-USB connector is shown, for example,as port 147 in FIG. 1C. The USB-type receptacle 5920 can be used, forexample, to connect to a wall plug to charge the host mobile device 110and/or the mobile device cover 100, or to connect to another USB-typecompatible device. In addition, the circuit 5900 also enables powertransfer and synchronization between the host mobile device 110 and themobile device cover 100.

FIG. 60 shows an exemplary battery charge indicator circuit 6000 of themobile device cover 100 according to an embodiment of the presentdisclosure. The exemplary battery indicator circuit 600 is operativelycoupled to one or more processors of the mobile device cover 100. Theone or more processors send signals that cause the light drivercircuitry 6010 to light up 0 to 4 lights 160 as an indication of batterycharge of the battery 170 of the mobile device cover 100. For example, 0lights indicates no or little charge; 1 light indicates approximately25% battery charge; 2 lights indicate approximately 50% battery charge;3 lights indicate approximately 75% battery charge; and 4 lightsindicate full or almost full charge.

FIG. 61 shows an exemplary push button circuit 6100 according to anembodiment of the present disclosure. The pushing or releasing of abutton (e.g., button 3820) causes a switch 6110 to open or close,thereby allowing the one or more processors of the mobile device cover600 to sense when the button has been pressed or released, as well asdetermine a duration of time that the button is held down. In someembodiments, the button comprises any type of input device and/or sensor(e.g., capacitive sensor, proximity sensor, heat sensor, touch sensor,pressure sensor, electromagnetic sensor, motion sensor, gesture sensor,etc.).

FIG. 62 shows an exemplary memory circuit 6200 according to anembodiment of the present disclosure. The memory circuit 6200 can be incommunication with the one or more processors of the mobile device cover100. Referring to FIG. 62, one or more flash memories 6210 can be usedto store instructions (e.g., processor-executable instructions),software, code, commands, parameters, data, etc. The flash memories 6210can be used to store, for example, icons, light shows, contactinformation, settings, notifications, notification parameters, etc. inthe mobile device cover 100.

FIG. 63 shows an exemplary processor circuit 6300 according to anembodiment of the present disclosure. The processor circuit 6300 caninclude one or more processors 6310. For example, processor 6310 isshown as a digital signal processor with internal memory (e.g., cache,RAM, ROM, etc.). The processor 6310 can be operatively coupled with andcontrols the other circuits shown in FIGS. 59-70 in addition to othercircuitry of the mobile device cover 100 and/or the host mobile device110. Processor 6310 is the main processor of the mobile device cover100.

FIG. 64 shows an exemplary battery management circuit 6400 according toan embodiment of the present disclosure. Referring to FIG. 64, thebattery management circuit 6400 is operatively coupled to the battery170 of the mobile device cover 100 and/or the battery of the host mobiledevice 110. The battery management circuit 6400 includes a batterycharger 6410 that is operatively coupled to the battery 170 of themobile device cover 100 and/or the battery of the host mobile device110. When the mobile device cover 100 is plugged into a wall outlet, forexample, the battery charger 6410 charges one or both of the batteriesof the mobile device cover 100 and the battery of the host mobile device110 as well as powers the mobile device cover 100 and/or the host mobiledevice 110. The battery charger 6410 is also configured to charge thebattery of the host mobile device 110 from the battery 170 of the mobiledevice cover 100, or vice versa, and/or to power the mobile device cover100 and/or the host mobile device 110. The charging direction and otherstart- or stop-charging parameters can be set by the one or moreprocessors of the mobile device cover 100. The battery charger 6410 incombination with the one or more processors of the mobile device cover100 is also configured to sense the amount of battery charge in one orboth of the batteries of the mobile device cover 100 and the battery ofthe host mobile device 110.

FIG. 65 shows an exemplary power management circuit 6500 according to anembodiment of the present disclosure. Referring to FIG. 65, the powermanagement circuit 6500 provides a power distribution auto-switchingpower multiplexer 6510, regulator 6520, and a load switch 6530 (e.g.,power rail switch) to smoothly transition between multiple powersources, such as DC power (e.g., battery operated power) and AC power(e.g., wall plug power) to power the mobile device cover 100 and/or thehost mobile device 110. The regulator 6520 provides a regulated 3Voutput for use by system power of the mobile device cover 100.

FIG. 66 shows an exemplary off/on and/or reset circuit 6600 according toan embodiment of the present disclosure. Referring to FIG. 66, thecircuit 6600 includes a microcontroller 6610 that causes the mobiledevice cover 100 to turn off and then on. For example, if the button3820 is pressed and held down or otherwise actuated for at least aparticular duration, the mobile device cover 100 is powered off and thenpowered on. In some embodiments, this is a power reset or power on/offof the mobile device cover 100.

FIG. 67 shows an exemplary clock circuit 6700 according to an embodimentof the present disclosure. Referring to FIG. 67, the clock circuit 6700includes, for example, a clock 6710 and a crystal 6720 to provide areal-time clock for the mobile device cover 100 and/or the host mobiledevice 110. The clock 6710 can be set and can keep time and calendardata, and/or set an alarm. The clock 6710 can be used, for example, todisplay time and calendar information on the mobile device cover 100 andfor synchronization purposes. Other wireless communications can usedinstead of or in combination with Bluetooth wireless signals including,for example, IEEE 802.11 wireless signals, WLAN signals, wireless PANsignals, Zigbee signals, infrared signals, RF signals, near-fieldwireless signals, etc.

FIG. 68 shows an exemplary Bluetooth circuit 6800 according to anembodiment of the present disclosure. Referring to FIG. 68, theBluetooth circuit 6800 includes a Bluetooth module 6810. The Bluetoothmodule 6810 supports the Bluetooth standard by providing secure wirelessconnections. In some embodiments, the Bluetooth module 6810 includes oneor more internal antennas for Bluetooth communications. However, one ormore external Bluetooth antennas operatively coupled to the Bluetoothmodule 6810 are also within the scope of the present disclosure. TheBluetooth module 6810 of the mobile device cover 100 can be used, forexample, to wirelessly communicate with the host mobile device 110and/or with other Bluetooth-enabled wireless devices.

FIG. 69 shows an exemplary LED driver circuit 6800 according to anembodiment of the present disclosure. Referring to FIG. 69, the LEDdriver circuit 6900 includes, for example, LED drivers 6910, 6920. Eachexemplary LED driver 6910, 6920 can drive up to 144 LEDs and can beprogrammed via an I2C compatible interface, for example. LED driversthat drive more or less than 144 LEDs are also within the scope of thepresent disclosure. FIGS. 70A-D show exemplary arrays of LEDs driven bythe LED drivers 6910, 6920. For example, the 144 LEDs in FIGS. 70A-B canbe driven by LED driver 6910, and the remaining LEDs in FIGS. 70C-D canbe driven by LED drive 6920. An exemplary array of LEDs is formed froman 11×21 grid of LEDs, for example. Additional or fewer LED drivers andLEDs can be added to or removed from the mobile device cover 100 withoutdeparting from the scope of the present disclosure. In addition, screensor other types of displays with accompanying screen or display drivercircuits are also within the scope of the present disclosure.

FIGS. 71-75 show exemplary printed circuit boards (or layers) that makeup a printed circuit board (or multi-layer printed circuit board) 7100as shown in FIG. 71 according to an embodiment of the presentdisclosure. FIG. 71 shows the printed circuit board 7100 when the fourprinted circuit boards (or layers of a multi-layer printed circuitboard) 7200, 7300, 7400, 7500 are stacked and put together. FIG. 72shows an exemplary top printed circuit board (or top layer of amulti-layer printed circuit board) 7200 according to an embodiment ofthe present disclosure. FIG. 73 shows an exemplary second printedcircuit board (or second layer of a multi-layer printed circuit board)7300 according to an embodiment of the present disclosure. The secondprinted circuit board 7300 is disposed beneath the top printed circuitboard 7200. FIG. 74 shows an exemplary third printed circuit board (orthird layer of a multi-layer printed circuit board) 7400 according to anembodiment of the present disclosure. The third printed circuit board7400 is disposed beneath the second printed circuit board 7300. FIG. 75shows an exemplary bottom printed circuit board (or bottom layer of amulti-layer printed circuit board) 7500 according to an embodiment ofthe present disclosure. The bottom printed circuit board 7500 isdisposed beneath the third printed circuit board 7400.

Some embodiments provide that a mobile application can be downloadedonto the host mobile device 110 to provide a graphical user interfacethat can be used, for example, to control the mobile device cover 100.The mobile application can run on the host mobile device 110 and/or themobile device cover 100. The graphical user interface can be on the hostmobile device 110 and/or the mobile device cover 100. Further, themobile application can be automatically or manually updated, upgraded,modified, replaced, overwritten, supplemented, etc. via a wireless orwired connection.

FIGS. 3 and 4 show an exemplary launch screen page 300 and an exemplaryfront page 400 according to an embodiment of the present disclosure. Themobile application can be represented as an icon (e.g., a graphicalelement of a graphical user interface) on the display (e.g., screen) ofthe host mobile device 110 and/or the mobile device cover 100. When theicon is selected, the mobile application runs on the host mobile device110 (and/or the mobile device cover 100) and a launch page 300 as shownin FIG. 3 is displayed by the host mobile device 110 (and/or the mobiledevice cover 100). Subsequently, a front page 400 as shown in FIG. 4 isdisplayed. While the front page 400 is being displayed, the mobileapplication attempts to wirelessly and/or wiredly connect the hostmobile device 110 and the mobile device cover 100 according to anembodiment of the present disclosure. In one embodiment, the mobileapplication attempts to wirelessly pair the mobile device cover 100 andthe host mobile device 110, which are both Bluetooth-enabled. If themobile application is not successful in making a connection (e.g., aconnection between previously paired devices 100, 110), then aconnection page 500 is opened as shown in FIG. 5, or an alternativeconnection method can be established via, for example, a USB-typeconnection, WiFi connection, Bluetooth connection, Zigbee connection,etc. If a successful connection is made, then an exemplary home page 700is opened as shown in FIG. 7. If the connection is lost, then the mobileapplication opens the front page 400 or the connection page 500.

By selecting the pair icon 410 (e.g., graphical button) shown in FIG. 4,an exemplary connection page 500 according to an embodiment of thepresent disclosure as shown in FIG. 5 is opened that allows forconfiguring wireless and/or network connections. The connection page 500enables the user to select a device for pairing (e.g., a mobile devicecover 100) and/or a network for connection. The list 520 of devices canbe refreshed by a user gesture such as a swipe, for example, otherwise,the list is refreshed periodically. In some embodiments, selecting aparticular device such as a mobile device cover 100, for example,initiates a verification process such as a pin verification process, forexample. After a prompt from the mobile application, entry of thecorrect pin (e.g., supplied by the mobile device cover 100) within aparticular time limit or by a particular number of attempts causes themobile application to open the home page 700 shown in FIG. 7.Configuring of the mobile application and/or the mobile device cover 100can occur based on a selection or an input of a particular model numberor particular type of mobile device cover 100. Incorrect entry of thepin number within the particular time limit or after a particular numberof failed attempts causes the mobile application to open the front page400 or the connection page 500. By selecting a back icon 510, forexample, the mobile application navigates to the front page 400, theconnection page 500, or a previous page.

By selecting the information icon 420 (e.g., an “i” icon) in FIG. 4, anexemplary instructions page 600 according to an embodiment of thepresent disclosure as shown in FIG. 6 is opened which providesdescriptions and helpful information about various items beingdisplayed, for example, on a push button or element selectable menu. Bytapping or toggling the back icon 610 (e.g., back graphical button), forexample, by making a gesture on the screen (e.g., swiping left to righton the screen), or by moving the mobile device cover 100 and/or hostmobile device 110 in a particular way, the home page 700 as shown inFIG. 7 or a previous page can be opened.

FIG. 7 shows an exemplary home page 700 according to an embodiment ofthe present disclosure. In some embodiments, upon successful connectionand pairing, the mobile application displays a home page 700 as shown inFIG. 7. The home page 700 provides a graphical user interface by whichthe user can further navigate the mobile application. Referring to FIG.7, the home page 700 includes icons or hyperlinks to open, for example,a phone page, a messages page, an email page, anotifications-for-applications page, a lighting-for-contacts page, abattery page, a lighting page, a back design page, and a settings page.In addition, the home page 700 provides for controlling a brightness(e.g., via a brightness slider 710) of a display and/or a volume for aspeaker for the mobile device cover 100 and/or the host mobile device110. In some embodiments, the home page 700 provides an icon 720 (e.g.,a graphical element) that can be toggled on or off as to whether todisplay incoming notifications on the mobile device cover 100, forexample.

In some embodiments, the mobile application enables the user with theability to set up a particular lightshow, a particular icon (e.g., anicon, an emoji, a custom-designed graphical element), and/or aparticular text (e.g., scrolling text) to be displayed for a particulartype of communication (e.g., phone, message, email. etc.), a particularcontact, and/or a particular type of communication (e.g., phone,message, email, etc.) for that particular contact on a contact liststored in the host mobile device 110 and/or the mobile device cover 100.The mobile application also enables the user to customize the selectedlightshow, icon, text, etc.

By selecting the phone icon 730 on the home page 700, a phone page 800according to an embodiment of the present disclosure is opened as shownin FIG. 8. In some embodiments, a messages page and an email page areopened by selecting the message icon 735 and the email icon 745,respectively, of the home page 700 and operate in a similar manner asthe phone page 800. In some embodiments, after the phone icon 730 isselected, a lightshows page 810 (e.g., for phone notifications) is firstshown for the phone page 800 as in FIG. 8; however, other selectableoptions including an icons page and a scrolling text page can also beopened by selecting the corresponding icons 820, 830 (e.g., graphicalbuttons or tabs). Referring to FIG. 8, the lightshows page 810 providesone or more graphical elements on a graphical user interface that enablethe user to select a particular lightshow (e.g., flare) from a list oflightshows that can be assigned, for example, to a particular contact.Parameters for the lightshows are also selected. For example, a speedand a duration are set (e.g., via graphical sliders 840, 850 as shown inFIG. 8) for the selected lightshow, which includes animation, forexample. Other adjustable or selectable parameters can include lightintensity, colors, size, pulsing, bursting, etc. The selected lightshowwith any selected particular lightshow parameters is assigned to aparticular contact (e.g., phone contact, phone number, etc.), and thisinformation is sent to the mobile device cover 100, for example. Theassignments are stored in the mobile device cover 100, the host mobiledevice 110, and/or the mobile application. The lightshows page 810provides an icon 860 (e.g., a preview-on-case icon) that, when selected,causes the mobile device cover 100 to demonstrate the currently selectedlightshow according to the selected lightshow parameters on the LEDs (orother lights or lighting devices) and/or on one or more screens of themobile device cover 100. In some embodiments, the lightshows page 810can provide an icon (e.g., a preview-in-the-mobile application icon) orcan automatically display in a portion 870 of the lightshows page 810 orin a separate page of the mobile application, a preview of the selectedlightshow according to the set lightshow parameters. For example, themobile application can provide a separate preview page or previewsection 870 as shown in FIG. 8 of the lightshows page 810 that shows theselected lightshow according to the selected settings (e.g., with anyselected animation at a particular speed for a particular duration) onan image of the mobile device cover 100 according to the selected modeland/or other characteristics (e.g., a blue back design or color). Thepreview in the mobile application can provide the user with a preview ofthe selected lightshow and lightshow options (e.g., on the host mobiledevice 110) without necessarily demonstrating the lightshow on the LEDsand/or screen of the mobile device cover 100. However, the preview inthe mobile application (e.g., on the host mobile device 110) can also beplayed concurrently or separately from with a preview on the case (e.g.,a preview using the LEDs and/or screen of the mobile device cover 100).In some embodiments, the lightshows page 810 provides an icon that, whenselected, enables a user to download or purchase (e.g., as part of anin-application purchases page) additional lightshows or features. Insome embodiments, clicking on a share icon enables the user to share theparticular lightshow, icon, and/or scrolling text with others (e.g.,friends, selected individuals, contacts, etc.). The sharing can befacilitated via a wired and/or wireless communication or transfer, atext, an email, a social media post or communication, etc. as text, afile, a graphics interchange format (GIF) file, an image, a video, apicture, a file stored in camera roll, etc. Selecting the back button880 (or other actions such as backwards swipes) brings back the homepage 700 or a previous page. Selecting (e.g., tapping or some other userinput) on the assigned contacts button or link 890 causes an assignedcontacts page 900 to open as shown in FIG. 9.

FIG. 9 shows an exemplary assigned contacts page 900 according to anembodiment of the present disclosure. The assigned contacts page 900enables the user to view and select a particular lightshow (e.g., lightpattern, lightshow, animation, etc.) for assignment (e.g., assignment orre-assignment). In some embodiments, a lightshow includes a series ofimages that are displayed on the mobile device cover 100 and/or themobile application. The assigned contacts page 900 also enables the userto view the currently assigned lightshow for a particular notificationcategory (e.g., email, message, phone, etc.). Further, the assignedcontacts page 900 can also identify duplicate lightshow assignments.Colors or other indicators enable the user to easily see duplicateassignments. Referring to FIG. 9, the Halo lightshow, which is shown asa red button 910, is assigned both to contacts Adam Fee and Abc Xyz. Theparticular colors used are merely exemplary. The Star lightshow, whichis shown as a blue button 920, is uniquely assigned to Amanda Bee. Theemail icon, the message icon, the phone icon, and the Happy icon, whichare shown as green buttons 930, indicate uniquely assigned icons foremails generally, messages, phone calls generally, and Ally Arm.Selecting the back button 940 (or other actions such as backwardsswipes) brings back a previous page (e.g., the lightshows page 810).

Selecting the icons button 820 (e.g., graphical tab) at the top of thephone page 800 shown in FIG. 8 opens an exemplary icons page 1000according to an embodiment of the present disclosure as shown in FIG.10. The icons page 800 of the mobile application enables the user toselect a particular icon, icon parameters, and/or animation forassignment (e.g., assignment or re-assignment). Selecting a particularicon such as, for example, the phone icon 1010 as shown in FIG. 10,causes the mobile application to display the phone icon as it would lookwhen displayed on the mobile device cover 100 on a portion 1020 of thepage 1000 or on a separate page. Information relating to the selectionof the phone icon 1010 including any icon parameters and assignments issent to the mobile device cover 100. By selecting the animations button1030, different types of animations are listed for application to thephone icon, for example. In some embodiments, the list includes onlythose animations that are applicable for the selected icon. In someembodiments, the animations can include moving across the screen,pulsating, bursting, dynamically changing colors, rotating, dynamicallychanging in size, etc. Selecting an icon parameter such as, for example,an animation, causes the mobile application to display the selected iconon a portion 1020 of the display according to the selected animationsand/or icon parameters, and to send the icon-related information to themobile device cover 100. Icon parameters such as a speed and a durationare set (e.g., via graphical sliders 1040, 1050 as shown in FIG. 10) forthe selected icon and the applied animation. In some embodiments, theicons page 1000 provides an icon 1060 (e.g., a preview-on-case icon)that, when selected, causes the mobile device cover 100 to demonstratethe currently selected icon according to the selected parameters and/oranimations on the mobile device cover 100 as shown in FIG. 25C, forexample. For example, the lights 160 (e.g., LEDs, screens, etc.) of themobile device cover 100 light up according to the selected icon,animations, and/or parameters to preview the response of the mobiledevice cover 100 for the particular assignment (e.g., a particularcontact, type of communication, type of notification, alert, etc.). Insome embodiments, the icons page 1000 can provide an icon (e.g., apreview-in-the-mobile application icon) or can automatically display ina portion 1020 of the icons page 1000 as in FIG. 10 or 25A, or in aseparate page 2500 of the mobile application as in FIG. 25B, a previewof the selected lightshow according to the set lightshow parameters. Thepreview changes as the user makes changes. The mobile application canalso provide a separate preview page 2500 as shown in FIG. 25B orpreview section 1020 as shown in FIG. 10 (or FIG. 25A) of the icons page1000 that shows the selected icon according to the selected settings(e.g., with any selected animation at a particular speed for aparticular duration) on an image of the mobile device cover 100according to the selected model and/or other characteristics (e.g., ablue back design or color). The preview in the mobile application canprovide the user with a preview of the selected icon and icon options(e.g., on the host mobile device 110) without necessarily demonstratingthe icon on the LEDs and/or screen of the mobile device cover 100.However, the preview in the mobile application (e.g., on the host mobiledevice 110) can also be played concurrently with a preview on the case(e.g., a preview using the LEDs and/or screen of the mobile device cover100) as shown in FIG. 25C. In some embodiments, clicking on a share iconenables the user to share the particular lightshow, icon, and/orscrolling text with others (e.g., friends, selected individuals,contacts, etc.). The sharing can be facilitated via a wired and/orwireless communication or transfer, a text, an email, a social mediapost or communication, etc. as text, a file, a graphics interchangeformat (GIF) file, an image, a video, a picture, a file stored in cameraroll, etc. Selecting the back button 880 (or other actions such asbackwards swipes) brings back the home page 700 or a previous page.

In some embodiments, the icons page 1000 provides an icon that, whenselected, enables a user to download or purchase (e.g., as part of anin-application purchases page) additional icons or features. Selectingthe back button 1070 (or other actions such as backwards swipes) bringsback the home page 700 or a previous page.

Selecting the scrolling text button 830 (e.g., graphical tab, graphicalelement, etc.) at the top of the phone page 800 shown in FIG. 8 or thescrolling text button 1080 at the top the icons page 1000 shown in FIG.10 opens an exemplary scrolling text page 1100 according to anembodiment of the present disclosure as shown in FIG. 11A. The scrollingtext page 1100 enables the user to select a text and/or a scrolling textand/or scrolling text parameters for assignment (e.g., assignment orre-assignment). Selecting text, scrolling text, and/or scrolling textparameters causes the mobile application to send the selected text,scrolling text, and/or scrolling text parameters to the mobile devicecover 100. Referring to FIG. 11B, an exemplary scrolling text page 1105is shown with a preview pane 1115 that enables the viewing of thescrolling text (e.g., customized scrolling text, preset scrolling text,etc.). The speed and text can be changed using the scrolling text page1105. Further, as will be explained below with respect to FIGS. 25D-E,for example, the font and the orientation of the scrolling text can bechanged and previewed. The preview changes as the user makes changes tothe scrolling text. The preview pane 1115 can also be a pop-up window ora separate page. The previewed pane 1115 can also illustrate variouschanges in the scrolling text on a representation of a selected model ofthe mobile device cover 100. Further, the previewed display can also beactually displayed on the mobile device cover 100 to view the display(e.g., scrolling text display) in view of any scrolling text changes,for example. In some embodiments, clicking on a share icon 1125 enablesthe user to share the scrolling text (and/or particular lightshow, icon,etc.) with others (e.g., friends, selected individuals, contacts, etc.).The sharing can be facilitated via a wired and/or wireless communicationor transfer, a text, an email, a social media post or communication,etc. as text, a file, a graphics interchange format (GIF) file, animage, a video, a picture, a file stored in camera roll, etc.

By selecting an icon 1110 (e.g., a plus icon), an exemplary add itempage 1200 according to an embodiment of the present disclosure is openedas shown in FIG. 12. The add item page enables a user to select textoptions for scrolling on the mobile device cover 100. Referring to FIG.12, a user can add words, symbols, names, a phone type, and/or a phonecharacter for scrolling. A user can cause the word “Call” to scrollacross the mobile device cover 100 as part of a phone call notificationor as part of a calendar alert, for example. In addition, differentoptions for scrolling the name of the caller are available such as thefull name, first name, first name and remaining name in initials, allinitials, etc. Furthermore, the user can add a phone type, a phonecharacter, or some other customized graphics for scrolling across themobile device cover 100 as part of a notification, for example.Selecting the back button 1210 (or other actions such as backwardsswipes) brings back the scrolling text page 1100.

Referring back to FIG. 11, further options for scrolling includechanging the order and appearance of words, names, phone type, phonecharacter, and/or icon for scrolling. The order of these options can bechanged, for example, by moving the particular category of informationbeing scrolled into a different position in the display order 1120 byselecting and moving the three lined icon 1130. The scrolling text page1100 enables, via one or more graphical elements 1140, a user to displaythe icon before or after the scrolling text, or not at all. Thescrolling text page 1100 further enables the user to select a type ofseparator, via a selection menu 1150, between different categories(e.g., name, phone character, phone type, etc.) for scrolling. Forexample, the separator can be one or more lines or spaces betweendifferent categories (e.g., phone character, name, phone type, icon,etc.). In addition, the scrolling text page 1100 provides for the userto determine, via selection menus 1160, 1170, the number of displayrepetitions (e.g., one, two, three, etc.) of the scrolling message and ascroll speed. In some embodiments, the scrolling text page 1100 providesan icon 1180 (e.g., a preview-on-case icon) that, when selected, causesthe mobile device cover 100 to demonstrate the currently selectedscrolling text and/or icon according to the selected scrolling textparameters and/or animations on the mobile device cover 100. In someembodiments, the mobile application can preview the scrolling text onthe host mobile device 110, for example, as part of the lightshows page810, the icons page 1000, the scrolling text page 1100, or a separatepage, the selected scrolling text with or without accompanying icons orlightshows according to the scrolling text parameters and/or otherparameters as it would appear on the mobile device cover 100. Forexample, the mobile application can provide a preview page that includesan image of the mobile device cover 100 (e.g., the selected modelincluding color and other characteristics of that model of the mobiledevice cover 100) with the scrolling text as it would appear on themobile device cover 100 during a notification or other display, forexample. Selecting the back button 1190 (or other actions such asbackwards swipes) brings back the home page 700 or a previous page.

In some embodiments, by selecting a notifications-for-applicationsbutton or link 740 (e.g., graphical element in a graphical userinterface, the text “Notifications for App,” etc.) on the home page 700as shown in FIG. 7, an exemplary notifications-for-applications page1300 is opened as shown in FIG. 13. The notifications-for-applicationspage 1300 enables users to view and change settings for applications forwhich the mobile application and the mobile device cover 100 supportcustom notifications. Referring to FIG. 13, a list of applications 1310is shown for which the mobile application and the mobile device cover100 support notifications. Some embodiments provide that the list ofmobile applications include the mobile application installed on the hostmobile device 110, any of the user's other host mobile devices or mobiledevices, the mobile device cover 100, etc. For each listed application,the user can select (e.g., tap, toggle, etc.) various options. In someembodiments, a button or icon (e.g., a graphical element of a graphicaluser interface) is provided to turn on or off a particular notificationparameter. Referring to FIG. 13, for each listed application, agraphical button 1320 is provided to turn on or off the displaying ofnotifications from the calendar application on the mobile device cover100, for example. A graphical button 1330 is also provided for eachlisted application to turn on or off the displaying of the respectiveapplication name (e.g., Amazon, Calendar, etc.) on the mobile devicecover 100 when the mobile application receives a notification for therespective application. A graphical button 1340 is provided for eachlisted application to turn on or off the displaying of a particular icon(e.g., application icon, customized icon, emoji, etc.) corresponding tothe respective application when the mobile application receives anotification for the respective application. In addition, a graphicbutton 1350 is provided for each listed application to turn on or offthe displaying of the contents of a notification (e.g., scrolling thecontents of a notification on the mobile device cover 100, text or mediafrom an email, a message, a textual alert, a sound, a transcription of avoicemail, etc.) when the mobile application receives the notificationfor the respective application. The notifications-for-applications pagealso provides a search bar 1360 for searching for applications by name,for example. Selecting the back button 1370 (or other actions such asbackwards swipes) brings back the home page 700 or a previous page.

In some embodiments, by selecting a lighting-for-contacts button or link750 (e.g., graphical element in a graphical user interface, the text“Lighting for Contacts,” etc.) on the home page 700 as shown in FIG. 7,an exemplary lighting-for-contacts page 1400 is opened as shown in FIG.14. The lighting-for-contacts page 1400 enables users to view and assignlightshows, icons, scrolling text, etc. for display on the mobile devicecover 100, for example. Referring to FIG. 14, by selecting (e.g.,tapping or some other user input) a contact name 1410 or a graphicalbutton 1420 indicating an assigned lightshow, icon, etc., alightshows-for-contacts page 1500 or an icon-for-contacts page 1600 isopened as shown in FIG. 15 or 16, respectively. In some embodiments,swiping left to right or right to left on the contact name 1410 or thegraphical button 1420 indicating an assigned lightshow or icon, forexample, causes the removal of the particular contact and/or thelightshow or icon assignment for a particular contact. The screenincluding the data displayed on the screen can be refreshedcontinuously, periodically, or aperiodically by a gesture (e.g., a swipeup or down, selecting a graphical element, etc.) on the screen.Selecting the back button 1430 (or other actions such as backwardsswipes) brings back the home page 700 or a previous page.

FIG. 15 shows an exemplary lightshows-for-contacts page 1500 accordingto an embodiment of the present disclosure. In particular, by selectingthe contact name, e.g., Hank Williams, or a graphical button indicatinga lightshow assigned to Hank Williams on the lighting-for-contacts page1400, the exemplary lightshows-for-Hank-Williams page 1510 opens asshown in FIG. 15. The lightshows-for-contacts page 1500 enables a userto change the lightshow and lightshow parameters assigned to aparticular contact. The current lightshow for Hank Williams is listed asthe Star lightshow 1520; however, other lightshows can be selected(e.g., by tapping or toggling on the lightshow name such as “Nova”) fromthe lightshows list 1530 for assignment to Hank Williams. Parameters forthe selected lightshow such as a speed (e.g., speed of an animation ofthe lightshow) and a duration of the lightshow care are controlled bysliding controls 1540, 1550 (e.g., graphical sliders). Data relating tothe selected lightshow and lightshow parameters is sent to the mobiledevice cover 100. The selected lightshow is shown or previewed on aportion 1560 of the lighting-for-contacts page 1500 including anyselected animations in accordance with any selected lightshowparameters. The preview also reflects the selected model including coloror other characteristics (e.g., arrangement of LEDs or screens,resolution, etc.) of the selected model of the mobile device cover 100so that the user can see how the lightshow looks on the selected modelof the mobile device cover 100. The lightshows-for-contacts page 1500also provides an icon 1570 (e.g., a preview-on-case icon) that, whenselected, causes the mobile device cover 100 to demonstrate (e.g.,actually display on the mobile device cover 100, cause LEDs of themobile device cover 100 to light according to the lightshow, animations,and parameters, cause screens of the mobile device cover 100 to displayaccording to the lightshow, animations, and parameters, etc.) thecurrently selected lightshow including any selected animations accordingto any selected lightshow parameters. Selecting (e.g., tapping or someother user input) on the assigned contacts button or link 1580 causesthe assigned contacts page 900 to open. In some embodiments, thelightshows-for-contact page 1500 provides an icon that, when selected,enables a user to download or purchase (e.g., as part of anin-application purchases page) additional lightshows or features.Selecting the back button 1590 (or other actions such as backwardsswipes) brings back the home page 700 or a previous page.

FIG. 16 shows an exemplary icons-for-contacts page 1600 according to anembodiment of the present disclosure. In particular, by selecting thecontact name, e.g., Hank Williams, or a graphical button indicating anicon assigned to Hank Williams on the lighting-for-contacts page 1400,the icons-for-Hank-Williams page 1610 opens as shown in FIG. 16.Alternatively, if the lightshows-for-Hank-Williams page 1510 is alreadyopened as shown in FIG. 15, then selecting the icons button 1595 (e.g.,graphical tab) also opens the icons-for-Hank-Williams page 1610. Theicons-for-contacts page 1600 enables a user to change the icon (e.g., anicon, an emoji, a graphical element, a custom-designed graphicalelement, a downloaded graphical element, a stored graphical element,etc.) and icon parameters assigned to a particular contact and/or for aparticular type of notification for the particular contact. For example,in addition to speed and duration parameters, the icons-for-contactspage 1600 can also add animation to the icon. Other parameters that canbe changed include, for example, parameters that change the color, size,intensity, pulsating, bursting, etc. of the icon. The informationindicating the selected icon and icon parameters is sent to the mobiledevice cover 100. The selected icon is shown or previewed on a portion1620 of the icons-for-contacts page 1600 (or on a separate page)including any selected animations in accordance with any selected iconparameters. The preview also reflects the selected model including coloror other characteristics (e.g., arrangement of LEDs or screens,resolution, etc.) of the selected model of the mobile device cover 100so that the user can see how the displayed icon looks on the selectedmodel of the mobile device cover 100. The icons-for-contacts page 1600also provides an icon 1630 (e.g., a preview-on-case icon) that, whenselected, causes the mobile device cover 100 to demonstrate (e.g.,actually display on the mobile device cover 100, cause LEDs of themobile device cover 100 to light according to the icon, animations, andparameters, cause screens of the mobile device cover 100 to displayaccording to the icon, animations, and parameters, etc.) the currentlyselected icon with any selected animations according to any selectedicon parameters. Selecting (e.g., tapping or some other user input) onthe assigned contacts button or link 1640 causes the assigned contactspage 900 to open. In some embodiments, the lightshows-for-contact pageprovides an icon that, when selected, enables a user to download orpurchase (e.g., as part of an in-application purchases page) additionalicons or features. Selecting the back button (or other actions such asbackwards swipes) brings back the home page 700 or a previous page(e.g., the lightshows-for-contacts page).

FIG. 17 shows an exemplary battery page 1700 according to an embodimentof the present disclosure that is opened, for example, when the batteryicon or link 760 on the home page 700 is selected. The battery page 1700enables a user to view and change the battery settings of mobile devicecover 100 and/or the host mobile device 110. For example, the batterypage 1700 enables a user to turn on an autocharging feature of themobile application. The user can set a start automatic chargingparameter and a stop automatic charging parameter. The parameters canbe, for example, battery charge percentages of the mobile device cover100 battery or the host mobile device 110 battery. In an exemplaryembodiment, a full battery charge is 100% and an exhausted batterycharge is 0%, for example. In addition to battery charge percentages,the parameters can be in units of energy, charge, power, capacity, etc.Each parameter is set by selecting (e.g., tapping, toggling, or someother user input) the increase (“+”) or decrease (“−”) graphical buttons1710 which incrementally increases or decreases the respective parameteraccordingly. In some embodiments, when the mobile application sensesthat the battery charge percentage of the host mobile device 110 batteryhas dropped to or below the start automatic charging parameter, then themobile application causes the mobile device cover 100 battery to chargethe host mobile device 100 battery until the stop automatic chargingparameter is reached. In some embodiments, similar automatic chargingparameters are used by the mobile application to also cause the hostmobile device 110 battery to charge the mobile device cover 100 battery.The parameters and information relating to whether the automaticcharging feature enabled is sent by the mobile application to the mobiledevice cover 100 and/or the host mobile device 110. By selecting themanual tab 1770, the battery page 1700 also enables to user to initiatemanual battery charging by selecting one battery (e.g., the mobiledevice cover 100 battery) to charge another battery (e.g., the hostmobile device 110 battery) according to a selectable condition (e.g.,battery charge, duration, etc.). The battery page 1700 also displays thebattery charge or battery charge percentages 1720, 1730 of the batteriesof the mobile device cover 100 and the host mobile device 110,respectively. When either battery is being charged, a charging icon 1740is displayed over the battery FIG. 1750 or over the portion 1760 of thebattery FIG. 1750 representing the battery that is being charged.Selecting the back button 1780 (or other actions such as backwardsswipes) brings back the home page 700 or a previous page.

FIG. 18 shows an exemplary lighting page 1800 according to an embodimentof the present disclosure that is opened, for example, when the lightingicon or link 770 on the home page 700 is selected. The lighting page1800 enables a user to set lighting settings for the mobile applicationand the mobile device cover 100. The lighting page lists a number oflighting options 1810 (e.g., flashlight, softlight, reading light,strobe light, panic light, etc.), the order of which can be changed bydragging the respective three lines icon 1820 corresponding to thelighting option to the appropriate place in the list. By selecting oneof the lighting options (e.g., flashlight, softlight, panic light,etc.), the respective light parameters 1830 (e.g., brightness via slider1840, duration via incremental adjustment buttons 1850, 1855, etc.) ofthe selected lighting option is viewed and can be modified. The mobiledevice cover 100 and/or the mobile application can operate according toone or more light options for a select time and/or duration, the one ormore light options provided by the mobile device cover 100 including: aflashlight; a soft light; a panic light (e.g., a bright bursting lightthat may accompany a piercing sound); a selfie light (e.g., a soft ringof light to naturally illuminate a face during a selfie and used inconjunction, for example, with a camera of the host mobile device 110 oran external camera); a reading light (e.g., an adjustable light forreading); a strobe light; icons (e.g., static or animated iconsincluding emojis displayed by one or more LEDs or on one or morescreens); light shows; light patterns; scrolling text (e.g., favoriteproverb or saying); and a clock. By selecting a respective icon (e.g.,an “i” icon 1860), a corresponding page (e.g., clock page, lightshowspage, icons page, etc.) opens. Referring to FIG. 18, when the flashlightoption is selected, the mobile device cover 100 operates as a flashlightby one or both of turning on selected LEDs or turning on one or morescreens to a particular brightness and/or hue, for example. The “on” and“off” tabs 1870, 1875 (e.g., icons, graphical elements, etc.) turn theflashlight on or off, respectively. The brightness and duration of theflashlight option can be set by a graphical slider 1840 or incrementaladjustment icons (e.g., “+” icon 1850 and “−” icon 1855). The variousoptions of the lighting page 1800 can be previewed in the mobileapplication (e.g., a portion of the lighting page 1800 or a separatepage) and/or on the mobile device cover 100 (and host mobile device110). As with all features described in the present disclosure, themobile device cover 100 operates whether physically connected to hostmobile device 110 or physically separated from the host mobile device110. Selecting the back button 1880 (or other actions such as backwardsswipes) brings back the home page 700 or a previous page.

In some embodiments, the lighting page 1800 provides the setup of apanic light, panic alert, hazards, blinkers, etc. For example, for usein an emergency situation, a user can enable the lighting page to set upa panic alert. The panic alert can be activated by a graphical button onthe lighting page 1800 or on a home screen of the host mobile device110, or a physical button on the host mobile device 110. The panic alertcan also be activated by a graphical button on a screen or a physicalbutton on the mobile device cover 100. The panic alert can include, forexample, a panic light that is a light pattern at the highestintensities in a pattern (e.g., bursting light pattern, full LED on/offblue or other light pattern) configured to draw the most attention tothe user and/or to disorient an attacker of the user, for example.Further, the panic alert can be accompanied with a loud sound or voicethat is broadcast over the speakers of the mobile device cover 100and/or the host mobile device 110. The sound or voice is configured todraw the most attention to the user and/or to disorient an attacker ofthe user, for example. The panic alert can also include, with or withouta prompt, the dialing of an emergency phone number (e.g., policedepartment, security system, emergency contact, etc.) and otherconfigurations such as turning on the speaker phone. Other options ofthe panic alert can include, for example, the sending of text messagesto various contacts notifying the various contacts of the emergencysituation. The messages and/or phone call can include locationinformation (e.g., via a satellite-based location determining systemsuch as GPS and/or a ground-based location determining system) or otherdata to direct responders to the user location. The camera on the hostmobile device 110 can be activated during a panic alert to take picturesat selected intervals and/or to take one or more movies, which can besent automatically and/or stored. These options can be set up for thepanic light link on the lighting page 1800 that can open up a menu or aseparate page for these panic alert settings and/or parameters.

FIG. 19 shows an exemplary clock page 1900 according to an embodiment ofthe present disclosure that is opened, for example, when the clock iconor link 1885 (e.g., the “Clock” link) on the lighting page 1800 isselected. The clock page 1900 enables a user to set clock settings fordisplay by the mobile device cover 100. Referring to FIG. 19, differentclock faces 1910 can be selected, for example, by swiping the clock facemenu options (e.g., vertical view, horizontal view, portrait view,landscape view, stop watch view, etc.). Different parameters 1920 can beset by corresponding icons (e.g., graphical toggle switches 1930). Forexample, the following parameters can be set to affect the clock displayon the mobile device cover 100: 12-hour time format, 24-hour timeformat, displaying leading zeroes, blinking colon, etc. Further, customfields can be selected and/or set. For example, custom fields can beused to further display and/or set calendar information, time zoneinformation, additional time zone information times, highlighted worldtime zone map, etc. In some embodiments, the clock page provides an icon1940 (e.g., a preview-on-case icon) that, when selected, causes themobile device cover 100 to demonstrate the currently selected clockaccording to the selected clock face and other clock parameters on themobile device cover 100. Selecting the back button 1950 (or otheractions such as backwards swipes) brings back the home page 700 or aprevious page (e.g., the lighting page 1800).

FIG. 20 shows an exemplary back design page 2000 according to anembodiment of the present disclosure that is opened, for example, whenthe back design icon or link 780 (e.g., icon and/or “Lighting” link) onthe home page 700 is selected. The back design page 2000 enables a userto select a particular back design and/or mobile device cover 100 model.Referring to FIG. 20, a listing 2010 of back designs can be viewed byswiping up or down, for example, on a touch-sensitive screen of the hostmobile device 110. Selection of a particular back design occurs byselecting (e.g., tapping, toggling, or some other user input) theparticular back design graphic 2020 or the back design description 2030(e.g., the “Blue” link). The selection of the particular back designand/or mobile device cover 100 model affects the available lightshows,icons, animations, etc. that are adjustable for the selected back designand/or mobile device cover 100 model. For example, each mobile devicecover 100 model and/or particular back design can have its ownarrangement of lights (e.g., LEDs, indicators, etc.), screens, and/orfeatures. Accordingly, the available lightshows, icons, animations, etc.available for display on the light arrangements and/or screens of theselected mobile device cover 100 model and/or back design vary accordingto the selected mobile device cover 100 model and/or back design.Further, the mobile application uses the selected mobile device cover100 model and/back design when displaying selected lightshows, icons,animations, etc. during a preview, for example. For example, when themobile application is running on the host mobile device 110, the hostmobile device 110 can preview the selected lightshow, icons, animations,etc. using a page (e.g., lightshows page, lightshows-for-contacts page,icons page, a preview page, etc.) of the mobile application. Thegraphical preview provided by a page of the mobile applicationincorporates the selected mobile device cover 100 model and/or backdesign (e.g., structural features, colors, etc.). Selecting the backbutton 2040 (or other actions such as backwards swipes) brings back thehome page 700 or a previous page.

FIG. 21 shows an exemplary settings page 2100 that is opened, forexample, when the settings icon or link 790 (e.g., settings icon or“Settings” link”) on the home page 700 is selected. The settings page2100 enables a user to view and change general settings and othersettings. For example, the settings page 2100 can be used to changefonts, languages, display orientation, etc. via its graphical userinterface. Referring to FIG. 25D, an exemplary scrolling text fonts page2530 is shown with a preview pane 2535 that enables the viewing and/orselection of different fonts such as, for example, rounded, condensed,boxed, and other font choices that are not shown. By a swipe or othergesture on a screen, for example, other font choices can be viewed.Further, the option of all text being in capitals is provided. Thepreview pane 2535 can also be a pop-up window or a separate page. Thepreviewed pane 2535 can also illustrate various changes in fonts on arepresentation of a selected model of the mobile device cover 100.Further, the previewed display can also be actually displayed on themobile device cover 100 to view the display (e.g., scrolling textdisplay) in view of any font changes, for example. Referring to FIG.25E, an exemplary scrolling orientation page 2550 is shown with apreview pane 2555 that enables the viewing and/or selection of differentorientations (e.g., whether the text scrolls up, down, left, right,whether the text is in landscape or portrait format, etc.) for thescrolling text. The preview pane 2555 can also be a pop-up window or aseparate page. The previewed pane 2555 can also illustrate variouschanges in orientation on a representation of a selected model of themobile device cover 100. Further, the previewed display can also beactually displayed on the mobile device cover 100 to view the display(e.g., scrolling text display) in view of any orientation changes, forexample. Some embodiments provide that the host mobile device 110 and/orthe mobile device cover 100 can determine, for example, whether the hostmobile device 110 and/or the mobile device cover 100 is upside down orsome other orientation, for example, via an internal gyroscope and/oraccelerometer, for example, and automatically re-orient the displayedinformation accordingly so that the displayed information is easily readby a user.

Referring back to FIG. 21, respective icons 2110 (e.g., graphicalswitches or graphical elements that can be selected or toggled) areselected to turn on or off corresponding categories of notifications.For example, phone notifications, message notifications, emailnotifications, alerts, application notifications, or other notificationssupported and displayed on the mobile device cover 100 and/or the hostmobile device 110 can be turned on or off. Further, by selecting an iconor link 2120, 2130, 2140 on the settings page 2100, anotifications-for-applications page 2200, a lightshows-for-contacts page2300, a synchronization/reset page 2400, etc. can be opened. Thesettings page 2100 also provides icons or links 2150, 2160 that open anabout page, a test functions page, and other settings pages. The aboutpage enables the user to view model or version details of the mobileapplication and/or the mobile device cover 100. In addition, an icon orlink 2170 is provided to facilitate the update of the mobile applicationon the host mobile device 110 and/or the mobile device cover 100, andthe software and/or circuitry on the mobile device cover 100. Selectingthe back button 2180 (or other actions such as backwards swipes) bringsback the home page 700 or a previous page.

FIG. 22 shows an exemplary notifications-for-applications settings page2200 according to an embodiment of the present disclosure that isopened, for example, when the notifications-for-applications icon orlink 2120 on the settings page 2100 is selected. Thenotifications-for-applications settings page 2200 enables a user to viewand make changes (e.g., generally or specifically) to parametersgoverning the display of application notifications on the mobile devicecover 100. Referring to FIG. 22, various parameters can be set by theuser. For example, the user can generally (or specifically) enable ordisable, via a graphical switch 2210, the application notificationsbeing shown on the mobile device cover 100 for phone notifications,message notifications, email notifications, application notifications,etc. When enabled, the user can then set other general or specificparameters for the application notifications. Thenotifications-for-applications settings page 2200 provides the user withan icon 2220 (e.g., graphical switch or graphical element that can betapped or toggled) that causes icons (e.g., icons, emojis, graphicaldesigns, animations, lightshows, light icons, scrolling text, etc.) tobe included or not included during an application notification displayedon the mobile device cover 100. Other parameters for general or specificapplication notifications that a user can view and modify includeturning on/off animations 2230 and/or text scrolling, and setting ascroll speed 2240, a type of separator 2250 between text and/or icons, anumber of repeat times 2260, etc. Selecting the back button 2270 (orother actions such as backwards swipes) brings back the home page 700 ora previous page (e.g., the settings page 2100).

FIG. 23 shows an exemplary lightshows-for-contacts settings page 2300according to an embodiment of the present disclosure that is opened, forexample, when the lightshows-for-contacts icon or link 2130 on thesettings page 2100 is selected. The lightshows-for-contacts settingspage 2300 enables a user to view and make changes (e.g., generally orspecifically) to parameters governing the display of contact lightshowson the mobile device cover 100. Referring to FIG. 23, various parameterscan be set by the user. For example, the lightshows-for-contactssettings page 2300 provides a sort order icon or link 2310 (e.g., thatprovides a pop up menu) that is selected to set a sorting parameter forcontacts (e.g., a list of contacts) in the mobile application, and adisplay order icon or link 2320 that is selected to set a displayparameter for contacts (e.g., first name before last name when a contactis displayed on the mobile device cover 100). Further, the lightshows,icons (e.g., light icons), scrolling text, etc. for the phone, message,email, etc. are enabled or disabled by icons 2330 (e.g., graphicalswitches or graphical elements that can be selected or toggled). Inaddition, content can be displayed on the mobile device cover 100including, for example, phone numbers, email addresses, transcriptionsof voice mails, the body of emails, the body of texts, attachments tothe emails or texts, etc. Different parameters can be generally be setfor the different types of communication, for example, to distinguishthem from each other. For example, once a particular category ofapplication notification has been enabled, animations can be turned onor off (e.g., via graphical switch 2340), particular animations can bechosen, and other animation characteristics (e.g., blink, fade, etc.) ofthe animations can be set (e.g., via menus links 2450, 2460) for thegeneral categories such as notifications for phone, messages, emails,etc. or for specific phone numbers, messages/emails from specificsenders, etc. In some embodiments, animations and animation parameterscan be set for groups (e.g., subsets) of contacts depending upon thetype of communication. Selecting the back button 2470 (or other actionssuch as backwards swipes) brings back the home page 700 or a previouspage (e.g., the settings page 2100).

FIG. 24 shows an exemplary synchronization/reset page 2400 that isopened, for example, when the synchronization/reset icon or link 2140 onthe settings page 2100 is selected. By selecting the reset-to-defaulticon or link 2410, the synchronization/reset page 2400 enables the userto reset the mobile application settings to original default values andclear contact lists and other information in the mobile application. Thedefault values and other information are sent to and/or stored in themobile device cover 100 and/or the host mobile device 110. By selectingthe sync-settings-with-case icon or link 2420, the synchronization/resetpage 2400 enables the user to synchronize the mobile application withthe mobile device cover 100, for example, by sending presentvalues/settings and other present information (e.g., present settings,contact lists, selected animations, icons, parameters, etc.) to themobile device cover 100 or vice versa. Further, by selecting therepair-LED-grid icon or link 2430, the synchronization/reset pageenables a rewrite of all sectors for the mobile device cover 100,including sectors that store light patterns, light shows, fonts, icons,animations, clock faces, graphical elements, graphical designs, etc. Thesynchronization/reset page 2400 also provides an icon or link 2440 forbacking up settings and/or other information to a cloud network. Themobile application also provides an icon 2450 for restoring settingsand/or other information of the mobile application and/or mobile devicecover 100 from settings and/or other information stored on the cloudnetwork. In some embodiments, selections made on thesynchronization/reset page 2400 include warnings about the informationbeing lost if the user proceeds with the synchronization, reset, repair,and/or restore. For example, resetting or synchronizing the mobileapplication and/or the mobile device cover 100 can cause the settingsand lookup tables (or other types of memory or storage) in the mobiledevice cover 100 to be overwritten. Selecting the back button 2460 (orother actions such as backwards swipes) brings back the home page 700 ora previous page (e.g., the settings page 2100).

Other embodiments of the present disclosure may provide a non-transitorycomputer readable medium and/or storage medium, and/or a non-transitorymachine readable medium and/or storage medium, having stored thereon, amachine code and/or a computer program having at least one code sectionexecutable by a machine and/or a computer, thereby causing the machineand/or computer to perform the steps as described herein.

Accordingly, aspects of the present disclosure may be realized inhardware, software, or a combination of hardware and software. Thepresent disclosure may be realized in a centralized fashion in at leastone computer system or in a distributed fashion where different elementsare spread across several interconnected computer systems. Any kind ofcomputer system or other apparatus adapted for carrying out the methodsdescribed herein is suited. A typical combination of hardware andsoftware may be a general-purpose computer system with a computerprogram that, when being loaded and executed, controls the computersystem such that it carries out the methods described herein.

Aspects of the present disclosure may also be embedded in a computerprogram product, which comprises all the features enabling theimplementation of the methods described herein, and which when loaded ina computer system is able to carry out these methods. Computer programin the present context means any expression, in any language, code ornotation, of a set of instructions intended to cause a system having aninformation processing capability to perform a particular functioneither directly or after either or both of the following: a) conversionto another language, code or notation; b) reproduction in a differentmaterial form. While the present disclosure has been described withreference to certain embodiments, it will be understood by those skilledin the art that various changes may be made and equivalents may besubstituted without departing from the scope of the present disclosure.In addition, many modifications may be made to adapt a particularsituation or material to the teachings of the present disclosure withoutdeparting from its scope. Therefore, it is intended that the presentdisclosure not be limited to the particular embodiment disclosed, butthat the present disclosure will include all embodiments falling withinthe scope of the appended claims

What is claimed is:
 1. A mobile phone cover for use with a mobile phone,comprising: a first frame that provides an opening through which ascreen of the mobile phone can be viewed; a second frame configured toreceive the mobile phone, wherein the first frame and the second frameenclose the mobile phone; and a third frame configured to be removablyattached to the second frame and to be interchangeable with a fourthframe, wherein the second frame is disposed between the first frame andthe third frame or between the first frame and the fourth frame, whereinthe first frame forms a front side of the mobile phone cover, whereinthe third frame or the fourth frame forms a back side of the mobilephone cover, wherein the fourth frame provides a functionality notprovided by the third frame when the fourth frame replaces the thirdframe in the mobile phone cover, wherein the fourth frame that replacesthe third frame has an external surface that faces a direction oppositeto a direction of the screen of the mobile phone when the second framereceives the mobile phone, wherein the external surface provides anoutput related to the functionality provided by the fourth frame that isnot provided by the third frame.
 2. The mobile phone cover according toclaim 1, wherein the fourth frame provides a projector, and wherein thethird frame provides does not provide the projector.
 3. The mobile phonecover according to claim 2, wherein the fourth frame is configured tohouse circuitry to support the functionality.
 4. The mobile phone coveraccording to claim 3, wherein the circuitry of the fourth frame isconfigured to be in wireless communication with other circuitry of themobile phone cover.
 5. The mobile phone cover according to claim 1,wherein the third frame has a different appearance than the fourthframe.
 6. The mobile phone cover according to claim 5, wherein thefourth frame comprises an output device that can be used by one or bothof the mobile phone cover and the host mobile device.
 7. The mobilephone cover according to claim 6, wherein the third frame does notcomprise the output device.
 8. The mobile phone cover according to claim1, wherein the third frame does not comprise a screen, and the fourthframe comprises a screen that can be used by one or both of the mobilephone cover and the mobile phone.